You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Manjula Peiris (JIRA)" <ji...@apache.org> on 2007/03/02 09:56:50 UTC
[jira] Commented: (AXIS2C-535) Axis2/C adds rampart handlers when
they are not engaged.
[ https://issues.apache.org/jira/browse/AXIS2C-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477229 ]
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: https://issues.apache.org/jira/browse/AXIS2C-535
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org