You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Dennis Sosnoski (JIRA)" <ji...@apache.org> on 2009/07/17 22:18:14 UTC

[jira] Created: (AXIS2-4435) Applying policy does not engage module

Applying policy does not engage module
--------------------------------------

                 Key: AXIS2-4435
                 URL: https://issues.apache.org/jira/browse/AXIS2-4435
             Project: Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: client-api
    Affects Versions: 1.5
            Reporter: Dennis Sosnoski


The org.apache.axis2.description.AxisDescription JavaDocs say "This method sets the policy as the default of this AxisDescription instance. Further more this method does the followings.

(1) Engage whatever modules necessary to execute new the effective policy of this AxisDescription instance. (2) Disengage whatever modules that are not necessary to execute the new effective policy of this AxisDescription instance. (3) Check whether each module can execute the new effective policy of this AxisDescription instance. (4) If not throw an AxisFault to notify the user. (5) Else notify each module about the new effective policy."

This does not appear to work, at least not when WS-SecurityPolicy is used. Even after setting the policy on an AxisOperation (directly, or by way of a client stub generated from a WSDL containing a WS-SecurityPolicy) you still need to call engageModule("rampart") on the ServiceClient - otherwise the policy is ignored.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.