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] Updated: (AXIS2-4049) Modules not engaged at message level.
Date Tue, 07 Jul 2009 08:12:14 GMT

     [ https://issues.apache.org/jira/browse/AXIS2-4049?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Stefan Vladov updated AXIS2-4049:
---------------------------------

     Affects Version/s: 1.5
    Remaining Estimate: 0.02h
     Original Estimate: 0.02h

> 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.5, 1.4.1
>         Environment: any
>            Reporter: Stefan Vladov
>             Fix For: 1.4.1
>
>   Original Estimate: 0.02h
>  Remaining Estimate: 0.02h
>
> 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.


Mime
View raw message