axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Damitha Kumarage (JIRA)" <>
Subject [jira] Resolved: (AXIS2C-535) Axis2/C adds rampart handlers when they are not engaged.
Date Thu, 01 Mar 2007 11:27:51 GMT


Damitha Kumarage resolved AXIS2C-535.

    Resolution: Fixed

This also happen in sandesha2(naturally). The problem is because in the sandehsa2_out_handler
I don't check whether the sandehsa2 is enaged. To do that we need a function in service or
message context to check whether a given module is engaged by providing module qname.
I added that function to svc.c. Now the problem is solved for sandesha2. This should also
solve the
rampart problem

> 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