axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanka Samaranayake (JIRA)" <>
Subject [jira] Commented: (AXIS2-1304) Enabling engage/disengage modules to AxisMessage
Date Thu, 09 Nov 2006 06:18:37 GMT
    [ ] 
Sanka Samaranayake commented on AXIS2-1304:


If you attach a policy to any wsdl entity for a service , say <wsdl:portType> that would
mean that there will alway be an effective policy for the messages. 

And we always engaged the required modules for the messages if there is an effective policy.

Hence the codegen will fail if there is a single policy attached at a higher level  even though
there are no policies attached at the messages level.

> Enabling engage/disengage modules to AxisMessage
> ------------------------------------------------
>                 Key: AXIS2-1304
>                 URL:
>             Project: Apache Axis 2.0 (Axis2)
>          Issue Type: New Feature
>          Components: kernel
>         Environment: Linux version 2.6.17-gentoo (root@highlander) (gcc version 3.3.5-20050130
(Gentoo, ssp-, pie-
> java version "1.4.2_12"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_12-b03)
> Java HotSpot(TM) Client VM (build 1.4.2_12-b03, mixed mode)
>            Reporter: Sanka Samaranayake
>         Assigned To: Deepal Jayasinghe
> In order to support policies that are attached at message levels, it is necessary to
enabling module engagement/ disengagement on AxisMessage 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message