[
https://issues.apache.org/jira/browse/TUSCANY-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673924#action_12673924
]
ant elder commented on TUSCANY-2845:
------------------------------------
The SVN revision numbers that have fixed this so far are:
744098 Change XMLTextMessageProcessor to override the createFaultMessage to
handle FaultExceptions
744151 Partial fix for exceptions for sca clients using text xml wireformat
744162 Update JAXWSFaultExceptionMapper to handle extra contsructor
and for the itest to test this:
744060,744067,744099,744102,744163
> Checked exceptions w/ default JMS wireFormat over <binding.jms> should
> serialize fault, not FaultException
> ----------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2845
> URL: https://issues.apache.org/jira/browse/TUSCANY-2845
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Reporter: Scott Kurz
>
> I realize the spec doesn't spell this out, but I think the most natural
> mapping to say, what we do in <binding.ws>
> would be to serialize the fault to XML and put it in a TextMessage, assuming
> that the other side can construct the appropriate
> exception from the fault.
> True this is very JAX-WS-ish, which a straight JMS programmer might not
> expect... but what else could we do, use java.lang.Exception somehow?
> Today the checked exc seems to result in the throwing of FaultException,
> which will only work if Tuscany is on both sides.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
