axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Manjula Peiris (JIRA)" <>
Subject [jira] Commented: (AXIS2C-535) Axis2/C adds rampart handlers when they are not engaged.
Date Fri, 02 Mar 2007 08:56:50 GMT


Manjula Peiris commented on AXIS2C-535:

In Rampart in clients incoming path we can't check whether the module is engaged when it is
engaged programmatically. To solve this I added a flag call enable_security to axis2_conf.
This flag is set from the out handler when it gets rampart as a engaed module from service.
So in the clients in path we can check this flag even though the service is null.

> Axis2/C adds rampart handlers when they are not engaged.
> --------------------------------------------------------
>                 Key: AXIS2C-535
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>            Reporter: Manjula Peiris
>            Priority: Critical
>         Attachments: patch.txt
> If we run normal Axis2/C samples after building rampart they fail. This is because Axis2/C
engine adds rampart handlers to its phases even  the module is not engaged in the axis2.xml.

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