axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Vladov (JIRA)" <j...@apache.org>
Subject [jira] Created: (AXIS2-4049) Modules not engaged at message level.
Date Fri, 26 Sep 2008 09:45:46 GMT
Modules not engaged at message level.
-------------------------------------

                 Key: AXIS2-4049
                 URL: https://issues.apache.org/jira/browse/AXIS2-4049
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: kernel
    Affects Versions: 1.4.1
         Environment: any
            Reporter: Stefan Vladov
             Fix For: 1.4.1


The method org.apache.axis2.context.MessageContext#isEngaged(String moduleName) only checks
whether the module defined by the given name has been engaged at the global axis configuration,
axis service group, axis service or axis operation levels but does not check the axis message.
Thus if a policy is applied on the message level and, say as a result rampart is engaged,
the isEngaged check will actually return FALSE and the RampartSender handler won't be executed.

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message