<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Log to XFormsServer at info level you mean? That would work, sure. But
the disadvantage would be that if you wanted to suppress
xforms-submit-error messages being logged you also have to suppress all
other INFO level XFormsServer messages.<br>
<br>
Adrian<br>
<br>
Erik Bruchez wrote:
<blockquote cite="
mid447ED174.1020909@orbe..." type="cite">Adrian,
<br>
<br>
Thanks, that sounds quite reasonable. Wouldn't it be enough to just
<br>
have the extra XFormsModelSubmission, and log the 404, etc. to the
<br>
usual XFormsServer logger?
<br>
<br>
-Erik
<br>
<br>
Adrian Baker wrote:
<br>
> I finally got around to doing this, since we couldn't deploy to
<br>
> production environments with the
<br>
> org.orbeon.oxf.xforms.processor.XFormsServer logger set to debug
(far
<br>
> too verbose), but yet we were missing xforms-submit-error events
which
<br>
> were silently causing forms to behave badly.
<br>
>
<br>
> What I've done is split out some of the XFormsServer debug calls
to two
<br>
> other loggers:
<br>
>
<br>
> - org.orbeon.oxf.xforms.event.events.XFormsSubmitErrorEvent
<br>
> By default logs the *message only* of the exception causing an
<br>
> xforms-submit-error at INFO level. Setting to DEBUG will log the
entire
<br>
> stack trace of the exception.
<br>
>
<br>
> - org.orbeon.oxf.xforms.XFormsModelSubmission
<br>
> By default logs nothing. Setting this to DEBUG will debug invalid
<br>
> instance documents.
<br>
>
<br>
> So this gives slightly finer control over logging & debugging
XForms.
<br>
> The default settings should be roughly suitable for a production
<br>
> environment where you still want errors like a 404 (eg a remote
server
<br>
> is down etc) logged, but little more. If you want to debug
validation
<br>
> problems in a form the XFormsModelSubmission logger can be used
for
<br>
> this, without necessarily having to go to the level of
XFormsServer,
<br>
> which logs every instance document every time there's an
interaction
<br>
> (useful in it's on right, but makes it hard to pick stuff out of
the noise).
<br>
>
<br>
> The downside is is that by default you will get a INFO message
every
<br>
> time someone tries to submit a form with invalid data, but this
comes
<br>
> back to the general XForms issue of detecting whether
<br>
> xforms-submit-error is caused by a remote server issue or a
validation
<br>
> issue.
<br>
>
<br>
> Adrian
<br>
<br>
<pre wrap="">
<hr size="4" width="90%">
--
You receive this message as a subscriber of the <a class="moz-txt-link-abbreviated" href="mailto:
ops-users@obje...">
ops-users@obje...</a> mailing list.
To unsubscribe: <a class="moz-txt-link-freetext" href="mailto:
ops-users-unsubscribe@obje...">mailto:
ops-users-unsubscribe@obje...</a>
For general help: <a class="moz-txt-link-freetext" href="mailto:
sympa@obje...?subject=help">mailto:
sympa@obje...?subject=help</a>
ObjectWeb mailing lists service home page: <a class="moz-txt-link-freetext" href="
http://www.objectweb.org/wws">
http://www.objectweb.org/wws</a>
</pre>
</blockquote>
<br>
</body>
</html>
opensubscriber is not affiliated with the authors of this message nor responsible for its content.
Delicious
Digg
reddit
Facebook
StumbleUpon
