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 "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2007/04/03 10:37:35 UTC

[jira] Updated: (AXIS2C-575) When a module is engaged at service level, it gets engaged at global level

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

Samisa Abeysinghe updated AXIS2C-575:
-------------------------------------

    Affects Version/s: 1.0.0

> When a module is engaged at service level, it gets engaged at global level
> --------------------------------------------------------------------------
>
>                 Key: AXIS2C-575
>                 URL: https://issues.apache.org/jira/browse/AXIS2C-575
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: 1.0.0
>         Environment: Windows XP
>            Reporter: Evanthika Amarasiri
>
> 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: axis-c-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-c-dev-help@ws.apache.org