axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ali Sadik Kumlali (JIRA)" <>
Subject [jira] Commented: (AXIS2-1834) AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
Date Thu, 07 Dec 2006 07:21:21 GMT
    [ ] 
Ali Sadik Kumlali commented on AXIS2-1834:

Yes, I would rather look into the real problem. But, AFAIK, SOAP/JMS implementation is not
standardized yet[1] and it is unknown how and where to put service name in ERP.

BTW, it would not be a problem if we ignore this issue in favour of AXIS2-1665.


Ali Sadik Kumlali


> AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
> ----------------------------------------------------------------------
>                 Key: AXIS2-1834
>                 URL:
>             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>
> 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:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message