cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel Kulp (JIRA)" <>
Subject [jira] [Assigned] (CXF-3776) Duplicate policy getting added with java-first approach
Date Tue, 30 Aug 2011 17:16:43 GMT


Daniel Kulp reassigned CXF-3776:

    Assignee: Daniel Kulp

> Duplicate policy getting added with java-first approach
> -------------------------------------------------------
>                 Key: CXF-3776
>                 URL:
>             Project: CXF
>          Issue Type: Bug
>          Components: WS-* Components
>    Affects Versions: 2.4.2
>         Environment: Local build
>            Reporter: Rajesh Kumar
>            Assignee: Daniel Kulp
>             Fix For: 2.4.3
>         Attachments:
>   Original Estimate: 24h
>  Remaining Estimate: 24h
> I am trying the latest CXF release 2.4.2 for adding policy using java-first approach.
The generated wsdl had two occurences of policy. 
> Since I put the "wsu:id"  attribute in wsp:Policy tag, two policies with the same id
got added in the generated wsdl. Also tried removing "wsu:id" attribute to avoid the duplicate
policy exception, but it failed at some other point with error message "Signature creation
failed" (please refer attached stack_trace_without_policy_id.txt).
> when I removed "implementorClass" attribute from jaxws:endpoint configuration it was
observed that the generated wsdl has only one instance of policy as expected, but the client
stub generation for some of my webservices failed when configured without implementorClass.
> Please refer the attached artifacts for code/configuration to reproduce the issue. generated
wsdl with duplicate policy is also attached.
> CXF / WSS artifacts used for the sample webapp are as below:
>  cxf-2.4.2.jar
>  cxf-manifest.jar
>  cxf-xjc-boolean-2.4.0.jar
>  cxf-xjc-bug671-2.4.0.jar
>  cxf-xjc-dv-2.4.0.jar
>  cxf-xjc-ts-2.4.0.jar
>  wsdl4j-1.6.2.jar
>  wss4j-1.6.2.jar

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message