axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Davanum Srinivas (JIRA)" <>
Subject [jira] Assigned: (AXIS2-1834) AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
Date Fri, 26 Jan 2007 01:42:49 GMT


Davanum Srinivas reassigned AXIS2-1834:

    Assignee: David Illsley


could you please take a look at this issue?


> AddressingBasedDispatcher doesn't dispatch according to the wsa:Action
> ----------------------------------------------------------------------
>                 Key: AXIS2-1834
>                 URL:
>             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>
> 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:
For additional commands, e-mail:

View raw message