Uploaded image for project: 'CXF'
  1. CXF
  2. CXF-3776

Duplicate policy getting added with java-first approach

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 2.4.2
    • 2.4.3
    • WS-* Components
    • None
    • Local build

    • Moderate

    Description

      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

      Attachments

        1. duplicate_policy_Issue.zip
          6 kB
          Rajesh Kumar
        2. HelloWorld_generated_wsdl_with_duplicate_policy.xml
          9 kB
          Rajesh Kumar

        Issue Links

          Activity

            People

              dkulp Daniel Kulp
              w_raj@yahoo.com Rajesh Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - 24h
                  24h
                  Remaining:
                  Remaining Estimate - 24h
                  24h
                  Logged:
                  Time Spent - Not Specified
                  Not Specified