[
https://issues.apache.org/jira/browse/TUSCANY-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673239#action_12673239
]
ant elder commented on TUSCANY-2845:
------------------------------------
Based on what Simon just said I've updated the JMS binding wireFormat.textXML
to unwrap the jaxws exception and set it as xml in a jms text message. I've
updated the jms-nonscaclient-exceptions so that it tests this for both object
and text xml messages.
We still need to clarify what we think it really needs to do based on what the
spec says, but i think what it does now is close to whats been asked for and
its easier to see what it does looking at the jms-nonscaclient-exceptions itest
and we can update as necessary.
Another remaining thing is what to to for unchecked exceptions? Currently even
with wireFormat.textXML they get returned as a JMS Object message containing a
org.osoa.sca.ServiceRuntimeException
> 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.
