Bug 1083770
Summary: | [GSS] (6.4.0) Java First WS-Policy duplicate PolicyReferences when using annotations and no separate Java Interface | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Kyle Lape <klape> | |
Component: | Web Services | Assignee: | Alessio Soldano <asoldano> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Rostislav Svoboda <rsvoboda> | |
Severity: | unspecified | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 6.2.0 | CC: | bbaranow, bmaxwell, jbliznak, kkhan | |
Target Milestone: | DR6 | |||
Target Release: | EAP 6.4.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Known Issue | ||
Doc Text: |
A bug exists in CXF this version of JBoss EAP that causes `PolicyReferences` to be duplicated when using Java First WS-Policy Annotations (such as @Policies). The resulting WSDL generates multiple 'PolicyReference' elements when there is no separate Java interface.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1103847 (view as bug list) | Environment: | ||
Last Closed: | 2019-08-02 07:27:06 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1087653, 1103627, 1103847, 1115213, 1143935 |
Description
Kyle Lape
2014-04-02 22:46:03 UTC
Flagged as Known Issue as ticket unresolved at the time of writing the release note. Now set to bug fix as requested in bug 1096876. A resolution needs to be added to the doc text, however. Set back to known issue. Flag reset in error. This should already be included in 6.3.0 since this fix was included in CXF 2.7.11: klape@localhost cxf$ git tag --contains eb5ac69120bc7799997740ff6817864039b55518 cxf-2.7.11 I still see reported issue in 6.3.0.ER8: Defining webservice with no interface like this: @WebService( serviceName = "HelloWorldServiceNoInterface", portName = "HelloWorld1", name = "HelloWorld1", targetNamespace = "http://www.jboss.org/jbossas/quickstarts/wshelloworld/HelloWorld1" ) @Policy(uri = "ws-policy/x509SecurityPolicy.xml", placement = Policy.Placement.BINDING) public class HelloWorldServiceNoInterface { @WebMethod @Policies({ @Policy(uri = "ws-policy/inputPolicy.xml", placement = Policy.Placement.PORT_TYPE_OPERATION_INPUT), @Policy(uri = "ws-policy/outputPolicy.xml", placement = Policy.Placement.PORT_TYPE_OPERATION_OUTPUT) }) public String sayHello() { return "Hello World!"; } } still results in multiple PolicyReference elements in wsdl: <wsdl:portType name="HelloWorld1"> <wsdl:operation name="sayHello"> <wsdl:input message="tns:sayHello" name="sayHello"> <wsp:PolicyReference URI="#Input_Security_Policy"/> <wsp:PolicyReference URI="#Input_Security_Policy"/> </wsdl:input> <wsdl:output message="tns:sayHelloResponse" name="sayHelloResponse"> <wsp:PolicyReference URI="#Output_Security_Policy"/> <wsp:PolicyReference URI="#Output_Security_Policy"/> </wsdl:output> </wsdl:operation> </wsdl:portType> <wsdl:binding name="HelloWorldServiceNoInterfaceSoapBinding" type="tns:HelloWorld1"> <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/> <wsp:PolicyReference URI="#X509SecurityPolicy"/> <wsp:PolicyReference URI="#X509SecurityPolicy"/> <wsdl:operation name="sayHello"> <soap:operation soapAction="" style="document"/> <wsdl:input name="sayHello"> <soap:body use="literal"/> </wsdl:input> <wsdl:output name="sayHelloResponse"> <soap:body use="literal"/> </wsdl:output> </wsdl:operation> </wsdl:binding> This should not block 6.3.0 release. It can be pushed to 6.3.1 if needed. Shifting to 6.4.0. Verified with 6.4.0.DR8 |