RE: RE : Accessing xforms-submit-error

The quicker, easier and Chiba-specific way might be to extend
ContextSubmissionHandler so that replace="instance", instead of being
unsupported, attempts to return a xml instance node stored in the chiba
context... ? Currently I'm using the ContextSubmissionHandler for the
actual submit, so I might explore this option first.

> -----Original Message-----
> From: chiba-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx 
> [mailto:chiba-developer-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx]
>  On 
> Behalf Of Adrian Baker
> Sent: Monday, 28 February 2005 5:33 p.m.
> To: chiba-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> Subject: [Chiba-developer] RE : Accessing xforms-submit-error
> 
> 
> As a workaround I was planning to store the errors on the 
> 'real' server in the session, and then have a handler on the 
> xforms-submit-error element which would retrieve this with a 
> 'server-side' lookup. Something like :
> 
> <xforms:instance id="notifications" xmlns="">
>       <notifications>
>               <errors>
>                       <error>(template error notification
> message)</error>
>               </errors>
>                                               
>               <messages>
>                       <message>(template notification
> message)</message>
>               </messages>
>       </notifications>                
> </xforms:instance>
> ...
> <submission id="getErrors" replace="instance" 
> ref="instance('notifications')/errors" .../> ... <action 
> ev:event="xforms-submit-error">
>     <send submission="getErrors"/>
> </action>
> 
> The notifications instance data is then bound to a nice 
> pretty repeating notifications area on the top of the form :)
> 
> All that remains is getting the server to provide the error 
> messages as the submit reply... I guess the proper portable 
> way to do this is XMLRPC? Could I run into any session issues 
> using this?
> 
> Adrian
> (sorry for 'fake' reply - this message never made it to my 
> client, so I had to cut & paste from sourceforge).
> 
> 
> --------
> From: Chris Picton <chibadev-list@xxxxx>
> Accessing xforms-submit-error  
> 2004-11-17 01:43
> 
>  Hi all
>  
>  This has been brought up before, but I was trying to get 
> some  clarification on it.
>  
>  1.  Is is possible to get the context info from an 
> xforms-submit-error  and display it to the user?
>  
>  2.  When My XML RPC Submission handler encounters a problem, 
> should I be  raising an XFormsSubmitError, or an 
> XformsException, which is wrapped by  an XFormsSubmitError by 
> Submission.java?
>  
>  3.  Would the following be the "correct" way of flagging an error?
>  
>  <xforms:action ev:event="xforms-submit-error">
>    <xforms:message level="modal">
>        A submission error occurred: <!-- Insert context error here -->
>    </xforms:message>
>  </xforms:action>
>  
>  Regards
>  Chris
>  -- 
>  Chris Picton <chibadev-list@xxxxx>
>  Tangent Systems
>  
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from 
> real users. Discover which products truly live up to the 
> hype. Start reading now. 
> http://ads.osdn.com/?ad_ide95&alloc_id396&op=ick
> _______________________________________________
> Chiba-developer mailing list 
> Chiba-developer-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@xxxxxxxxxxxxxxxx
> https://lists.sourceforge.net/lists/listinfo/chiba-developer
> 


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_ide95&alloc_id396&op=click