You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Kaushik Mukherjee (JIRA)" <de...@tuscany.apache.org> on 2009/03/05 21:59:56 UTC
[jira] Updated: (TUSCANY-2905) Default operation selection does not
implement third rule which is supposed to look for an operation name in the
root element of the XML payload
[ https://issues.apache.org/jira/browse/TUSCANY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kaushik Mukherjee updated TUSCANY-2905:
---------------------------------------
Attachment: TUSCANY-2905.patch
Modified files include:
org.apache.tuscany.sca.binding.jms.operationselector.jmsdefault.runtime.OperationSelectorJMSDefaultServiceInterceptor
> Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload
> ------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: TUSCANY-2905
> URL: https://issues.apache.org/jira/browse/TUSCANY-2905
> Project: Tuscany
> Issue Type: Bug
> Components: Java SCA JMS Binding Extension
> Reporter: Kaushik Mukherjee
> Attachments: TUSCANY-2905.patch
>
>
> Default operation selection does not implement third rule which is supposed to look for an operation name in the root element of the XML payload
> The Oasis spec adds a rule to default operation selection as follows:
> 290 • Otherwise, if the message is a JMS text or bytes message containing XML, then the selected
> 291 operation name is taken from the local name of the root element of the XML payload.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.