[
https://issues.apache.org/jira/browse/AXIS2-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Illsley resolved AXIS2-1834.
----------------------------------
Resolution: Won't Fix
I don't believe that dispatching the service based on the action is the correct
way to go for a couple of reasons. The most important one is that that would
requires actions to be unique over the full set of services deployed which
simply isn't possible once you introduce standard actions e.g. with WS-RM,
WS-Transfer etc.
A better solution would be to include the service name in a JMS header as
suggested by section 2.3.3 of the SOAP/JMS proposal sent out by glen daniels
[1]:
[Definition: soapjms:targetService] (xsd:string)
* Used by the service implementation to dispatch the service request.
*optional in IRI
* if specified MUST appear in the JMS message in the JMS property named
SOAPJMS_targetService.
If you want to have a further discussion about doing service dispatch on the
action, please raise it as a proposal on the axis-dev mailing list.
Thanks,
David
[1] http://marc.theaimsgroup.com/?l=axis-dev&m=116860712209251
> AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
> ----------------------------------------------------------------------
>
> Key: AXIS2-1834
> URL: https://issues.apache.org/jira/browse/AXIS2-1834
> Project: Axis 2.0 (Axis2)
> Issue Type: Improvement
> Components: kernel
> Affects Versions: 1.1
> Environment: Not important
> Reporter: Ali Sadik Kumlali
> Assigned To: David Illsley
> Attachments: patch.txt
>
>
> AddressingBasedDispatcher only looks at <wsa:To> field. But in some
> situations, service should be resolved from <wsa:Action>. Consider following
> scenario:
> - JMS transport is used
> - Sender doesn't and cannot be able to set message header property called
> SOAPAction
> In this case, service is not found as AddressingBasedDispatcher doesn't check
> <wsa:Action> field.
> I've added <wsa:Action> check to AddressingBasedDispatcher::findService() and
> successfully used over my custom JMS transport listener(Please look at
> AXIS2-1585 for more details regarding MDB based JMS transport.)
> Regards,
> Ali Sadik Kumlali
> P.S.: Patch was created under
> ...\branches\1_1\modules\kernel\src\org\apache\axis2\engine
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
