Adrian,

I also think it is reasonable to have submission error logged by
default, that is: in "info" priority. And as you say, we could log
them with a separate logger, so one could disable those if needed.
Erik what is your take on this?

Alex

On 2/27/06, Adrian Baker <adrian.baker@orio...> wrote:
>  Option [2] (enabling debugging for
> org.orbeon.oxf.xforms.processor.XFormsServer) is certainly
> helpful.
>
>  But it's pretty imprecise, because of the screeds of other debugging output
> which results from having this class set to debug (eg dumping of all
> instance documents). Sure this is all useful in it's own right, but it's a
> bit heavyweight just to find out you've misspelt a URL in your submission
> target. Certainly I couldn't turn this on by default in a production
> environment, whereas I do really need submission errors logged as standard
> in production.
>
>  How about logging submission errors to a more specific logger (eg
> org.orbeon.oxf.xforms.event.events.XFormsSubmitErrorEvent)?
> This could then be reasonably enabled full-time.
>
>  Personally I'd argue this logger be turned on by default because it's flat
> out impossible to determine the cause of an xforms-submit-error any other
> way. And there's nothing more frustrating - particularly for first time
> XForms authors - than watching absolutely nothing happen when you click on a
> 'Save' button: no errors displayed, no errors logged.
>
>  Adrian
>
>  Erik Bruchez wrote:
> Duane,
>
>  This is an excellent question.
>
>  From the XForms spec's point of view, if submission fails, an
> xforms-submit-error event is thrown and that's it, which is not extremely
> helpful. Some tips:
>
>  1. If you are using XML schema for instance validation and suspect that
> validation may be failing because validation doesn't pass, try using an
> online schema validator with your submitted XForms instance.
>
>  2. You can enable server-side logging for XForms with:
>
>  <category
> name="org.orbeon.oxf.xforms.processor.XFormsServer">
>    <priority value="debug"/>
>  </category>
>
>  in log4j.xml, the XForms instance that failed to be saved will be logged
> with some annotations.
>
>  This can help a little bit, but I agree that this is not enough. We have an
> RFE for a client-side XForms console, which would be the right place to
> provide useful information about submission:
>
> http://forge.objectweb.org/tracker/index.php?func=detail&aid=304142&group_id=168&atid=350210
>
>  This will be post-3.0 however.
>
>  -Erik
>
>  Duane Gran wrote:
>
>  Is there anyway to get a more elaborate error message for an xforms-
> submit-error event?  I find that I spend a lot of time feeling in the  dark
> for simple mistakes I make which prevent the form from saving.   Although I
> capture the event successfully, I'm often at a loss about  the cause of the
> error.
>
>  Duane
>
>
> ________________________________
>
>
> --
> You receive this message as a subscriber of the ops-users@obje...
> mailing list.
> To unsubscribe: mailto:ops-users-unsubscribe@obje...
> For general help: mailto:sympa@obje...?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>
>
> --
> You receive this message as a subscriber of the ops-users@obje...
> mailing list.
> To unsubscribe: mailto:ops-users-unsubscribe@obje...
> For general help: mailto:sympa@obje...?subject=help
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>


--
Blog (XML, Web apps, Open Source):
http://www.orbeon.com/blog/