axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Samisa Abeysinghe (JIRA)" <>
Subject [jira] Resolved: (AXIS2C-575) When a module is engaged at service level, it gets engaged at global level
Date Tue, 03 Apr 2007 09:27:32 GMT


Samisa Abeysinghe resolved AXIS2C-575.

    Resolution: Won't Fix
      Assignee: Samisa Abeysinghe

This is a "feature" in Axis2 architecture. If you engage the module in a service to a globle
phase, then that module gets engaged globally. Modules can use axis2_svc_is_module_engaged
method to check if the service being used has engaged a given module and act accordingly.

> When a module is engaged at service level, it gets engaged at global level
> --------------------------------------------------------------------------
>                 Key: AXIS2C-575
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: Current (Nightly)
>         Environment: Windows XP
>            Reporter: Evanthika Amarasiri
>         Assigned To: Samisa Abeysinghe
>             Fix For: 1.0.0
> Came across the following error when engaging modules. Below are the steps to reproduce
the error
> 1. Engaged the addressing module at service level by adding the <module ref="addressing"/>
to the services.xml of the mtom_client
> 2. Checked the axis2.xml, and the echo client to see if addressing is engaged at these
two levels and made sure that at none of these points addressing was engaged.
> 3. Executed the echo_client.exe and noticed that the soap envelope contains addressing
headers which means when engaging the modules at service level, they are being engaged globally

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