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

Christian Connert reopened CXF-2499:
------------------------------------


Sorry but I found out that I had a one little bug in my fix:

public EffectivePolicy getEffectiveClientResponsePolicy(EndpointInfo ei, 
BindingOperationInfo boi) {
        EffectivePolicy effectivePolicy = 
(EffectivePolicy)boi.getProperty(POLICY_INFO_RESPONSE_CLIENT);
        if (null == effectivePolicy) {
            EffectivePolicyImpl epi = createOutPolicyInfo();
            epi.initialise(ei, boi, this, true, false);                         
                     //  previously epi.initialise(ei, boi, this, true, true);  
      
            boi.setProperty(POLICY_INFO_RESPONSE_CLIENT, epi);
            effectivePolicy = epi;
        }
        return effectivePolicy;
  }

Christian

> (EffectivePolicyImpl/PolicyEngineImpl) Policy engine for ws security policy 
> (based on wsdl attachment) fails to apply message level policies
> --------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CXF-2499
>                 URL: https://issues.apache.org/jira/browse/CXF-2499
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>         Environment: System:
> 2.6.28-15-generic #52-Ubuntu SMP Wed Sep 9 10:48:52 UTC 2009 x86_64 GNU/Linux
> Java:
> java version "1.6.0_16"
> Java(TM) SE Runtime Environment (build 1.6.0_16-b01)
> Java HotSpot(TM) 64-Bit Server VM (build 14.2-b01, mixed mode)
> Apache CXF 2.2.3 (not in version list)
>            Reporter: Christian Connert
>            Assignee: Daniel Kulp
>             Fix For: 2.2.5
>
>         Attachments: EffectivePolicyImpl.java, Messages.properties, 
> PolicyEngineImpl.java
>
>
> The problem is caused by the initialisePolicy method in the 
> EffectivePolicyImpl.
> The original method decided which BindingMessageInfo is used based on the 
> boolean requestor, which results in always using the OutputBindingMessage on 
> server-side respective Input.- on the client side. To fix this I introduced a 
> new parameter (boolean request) which is used for this decisions. The 
> parameter has to be passed from different methods in the PolicyEngineImpl. 
> Thus I also slightly changed the PolicyEngineImpl.  
> Since I don't want to rebuild the jar I extended both classed, reimplemented 
> the necessary methods and registered them as policy engine in my cxf.xml.
> Thus I can't attach a patch, but I append the extended implementations.
> Greetings
> Christian

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

Reply via email to