[
https://issues.apache.org/jira/browse/AXIS2C-624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12507843
]
Damitha Kumarage commented on AXIS2C-624:
-----------------------------------------
Manjula,
As you said if the handler is added to a global phase I agree that the handler
developer should manage to
handle requests that are not intended for the module.
But in this case the module is not engaged globally. Say there are two
services X and Y. Say module M is engaged to service X only(by adding a
reference in services.xml). Also assume that a module handler H is added to
module M specific phase(by editing module.xml). Then if the module handler H is
invoked
for a request targeted for Y, it is absolutely wrong. This is exactly the
problem I was trying explain.
> module handlers are invoked for service even when module is not engaged for
> the serivce
> ---------------------------------------------------------------------------------------
>
> Key: AXIS2C-624
> URL: https://issues.apache.org/jira/browse/AXIS2C-624
> Project: Axis2-C
> Issue Type: Bug
> Reporter: Damitha Kumarage
> Priority: Blocker
>
> I can see that even when a module is not engaged to a service(globally or
> service wise) handlers of that module is invoked
> for that service. This happens both for in and out path.
> This must be due to a change done to the engine very recently. I can cleary
> remember this was working correctly when I was testing sandesha2/C for
> release 0.90
--
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]
