Another interop problem. The detail element of the fault you are getting is empty. Consider the statement in BPEL, section 11.3: anonymous wrote : [T]he WSDL 1.1 standard SOAP binding explicitly precludes mapping any information from an abstract fault message to a SOAP Fault other than the contents of the detail element. In other words, there is no standard way to relate the faultcode, faultstring and faultactor sub-elements of a SOAP Fault element to data visible to a WS-BPEL process. Even worse: anonymous wrote : This specification does not provide a resolution for this problem. It makes sense for these faults not no have a detail element, since they are system faults rather than business faults, much like unchecked vs. checked exceptions. I could raise something like jbpm:systemFault with a message containing the faultcode, faultstring and faultactor items and then pass that to the fault handling mechanism (not yet finished, unfortunately). This solution, and any other, would be nonportable, tough. This is a good issue to take to the OASIS TC :-)
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3917017#3917017 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3917017 ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
