[
https://issues.apache.org/jira/browse/TUSCANY-2905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dan Becker resolved TUSCANY-2905.
---------------------------------
Resolution: Fixed
Hello Kaushik,
Thanks for contributing the patch. I've applied it to the 1.x branch and run
unit, stests, and itests, and it passes.
I have a few suggestions for future patches that will help make it easier to
integrate and test:
1) Let us know whether the branch is for trunk or one of the branches.
2) Generate the diff from the module or higher level.
3) Provide a unit test in the patch that tests the positive and negative
aspects of the patch.
These steps make it easier to find which directory to apply the patch, and the
unit tests make it easy to see the fix in action.
> 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
> Assignee: Dan Becker
> 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.
