[ http://issues.apache.org/jira/browse/AXIS2-1834?page=comments#action_12456045 ] David Illsley commented on AXIS2-1834: --------------------------------------
Hi, Thanks for the patch. I've had a quick look and have a couple of thoughts: 1. Why is service dispatch based on wsa:To followed by operation dispatch based on wsa:Action not appropriate? 2. If we do this we effectively introduce a new restriction of actions having to be unique across all services (I'm not sure this is practical) 3. If we do this I think we'd need to take a different approach as iterating like that is probably pretty slow. David > AddressingBasedDispatcher doesn't dispatch according to the wsa:Action > ---------------------------------------------------------------------- > > Key: AXIS2-1834 > URL: http://issues.apache.org/jira/browse/AXIS2-1834 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Improvement > Components: kernel > Affects Versions: 1.1 > Environment: Not important > Reporter: Ali Sadik Kumlali > 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. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
