[ https://issues.apache.org/jira/browse/TUSCANY-2848?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673304#action_12673304 ]
Scott Kurz commented on TUSCANY-2848: ------------------------------------- I don't think we necessarily need to fix this. If we follow the <binding.ws> example, which uses the JAX-WS spec mapping between an exception in the Java runtime and the platform-neutral, schema-mappable fault carried by the exception, then we just need to worry about serializing the fault, and not the chained exceptions. This puts a burden on the bottom-up, interface.java programmer to understand this pattern when using checked Java exceptions with the text/xml wireformat. The alternatives would be to either start from WSDL, top-down, and generate the exception/fault, OR to use a different wireFormat, like wireFormat.jmsObject, in which Java serialization will be used and chained exceptions will be preserved (Of course that last alternative assumes a certain spec interpretation which hasn't been agreed upon, but I guess you could say that across the board). > Chained exceptions get lost when returning a checked exception with the JMS > binding with text xml wire format > ------------------------------------------------------------------------------------------------------------- > > Key: TUSCANY-2848 > URL: https://issues.apache.org/jira/browse/TUSCANY-2848 > Project: Tuscany > Issue Type: Bug > Affects Versions: Java-SCA-Next > Reporter: ant elder > > Chained exceptions get lost when returning a checked exception with the JMS > binding with text xml wire format. > It looks like the databinding framework is not including the cause > information when converting from the checked exception to XML in an OMElement -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.