[
https://issues.apache.org/jira/browse/TUSCANY-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673235#action_12673235
]
Simon Laws commented on TUSCANY-2845:
-------------------------------------
As the code stands the exception format will follow the wire format however the
exception will always be returned in a JMS Object message. There is no way to
control the format of the exception independently. So in the case of
wireFormat.textXML (currently the default format) the databinding is set up to
do our standard JAXWS based data tranfsformations and hence you get wrapped
exceptions. For other wireFormats the data just flows directly to the JMS
binding without transformation and hence you see the native faults. Still as
Object messages thought.
So a couple of thoughts. We need to...
Decide what formats and message types should be used to transfer faults for
each wire format including the default one.
Just a string in a Text message
Unwrapped exception in an Object message
Talk to the spec people about control of fault format.
> 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.
