Alex,

I can appreciate the end goal for exception handling.  Adding an attribute
to the config info for the delegation processor in the mean-time to simply
pass the soap fault as the processor output would meet the need that we
have.

Please let me know the details when they become available (attribute name,
location, nightly build) and I look forward to taking it for a test drive.

Thanks

Brian
                                                                            
                                                                            
                                                                            
                                                                            
                                                                            
                                                                            
   --- Brian S Battah <[EMAIL PROTECTED]> wrote:                                
                                                                            
    > I"m trying to show something intelligible in the case of a web        
   service                                                                  
    > call failure in the Delegation Processor.                             
                                                                            
    Hi Brian,                                                               
                                                                            
    First, let me say that we are not necessarily happy with the way        
    exceptions are handled right now in the Delegation processor :).        
                                                                            
    The long term plan is to support exceptions in XPL. This will enable    
   you                                                                      
    to catch in XPL an exception thrown by the Delegation processor, by     
   giving                                                                   
    you access to a document that describes the issue (in this case the     
   SOAP                                                                     
    fault would be embedded), and giving you a chance to "do something"     
    knowing that this issue happened. This is why the Delegation processor  
   or                                                                       
    SQL processor do no return a "fault document" when an issue happens,    
   but                                                                      
    throw an exception.                                                     
                                                                            
    Of course, today there is no mechanism in XPL to catch exceptions. So   
   in                                                                       
    the meantime, we could modify the Delegation processor to return the    
   SOAP                                                                     
    fault instead of throwing an exception. To keep backward                
   compatibility, we                                                        
    would only do this if a special attribute is set on <service> or        
    <operation> in the service interface (if present, the attribute on      
    <operation> overrides the attribute on <service>).                      
                                                                            
    Does that sound reasonable?                                             
                                                                            
    Alex                                                                    
                                                                            
                                                                            
                                                                            
                                                                            





-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
orbeon-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/orbeon-user

Reply via email to