[
https://issues.apache.org/jira/browse/TUSCANY-2845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12673226#action_12673226
]
ant elder commented on TUSCANY-2845:
------------------------------------
I've added an itest to test various exceptions:
https://svn.apache.org/repos/asf/tuscany/branches/sca-java-1.x/itest/jms-nonscaclient-exceptions/
That has two SCA services, one using JMS text xml messages the other using JMS
Object messages, which throw different types of exceptions, and the services
are invoked by non-SCA clients. Presently the Text message tests are commentted
out till we work out what the response messages should look like. The Object
message ones are enabled and seem like the jms binidng is doing the ok thing.
> 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.
