Uploaded image for project: 'JBoss Enterprise Application Platform 4 and 5'
  1. JBoss Enterprise Application Platform 4 and 5
  2. JBPAPP-8011

REPLACE_WITH_ACTUAL_URL does not work for soap12 addresses

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: EAP_EWP 5.1.2
    • Fix Version/s: EAP_EWP 5.2.0 ER5
    • Component/s: Web Services
    • Labels:
    • Environment:

      JBoss Enterprise Application Platform 5.1.2 with JBossWS CXF

    • Steps to Reproduce:
      Hide

      Deploy WSDL with soap:address and soap12:address (as below) and webServiceHost jbossws.undefined.host in jboss-beans.xml

      The soap12 address is never rewritten.

        <wsdl:service name="Service">
          <wsdl:port name="ServiceSoap" binding="tns:ServiceSoap">
            <soap:address location="REPLACE_WITH_ACTUAL_URL" />
          </wsdl:port>
          <wsdl:port name="ServiceSoap12" binding="tns:ServiceSoap12">
            <soap12:address location="REPLACE_WITH_ACTUAL_URL" />
          </wsdl:port>
        </wsdl:service>
      
      Show
      Deploy WSDL with soap:address and soap12:address (as below) and webServiceHost jbossws.undefined.host in jboss-beans.xml The soap12 address is never rewritten. <wsdl:service name= "Service" > <wsdl:port name= "ServiceSoap" binding= "tns:ServiceSoap" > <soap:address location= "REPLACE_WITH_ACTUAL_URL" /> </wsdl:port> <wsdl:port name= "ServiceSoap12" binding= "tns:ServiceSoap12" > <soap12:address location= "REPLACE_WITH_ACTUAL_URL" /> </wsdl:port> </wsdl:service>
    • Affects:
      Release Notes
    • Release Notes Text:
      Hide
      Previously, when <literal>jbossws.undefined.host</literal> was used as the value of the <systemitem>webServiceHost</systemitem> property in the <filename>jboss-beans.xml</filename> file, the <literal>REPLACE_WITH_ACTUAL_URL</literal> string was not replaced by the actual address when used in a WSDL definition as the value of the <systemitem>location</systemitem> attribute of the <systemitem>soap12.address</systemitem> element. This update fixes this issue and the <literal>REPLACE_WITH_ACTUAL_URL</literal> string is now replaced with the appropriate SOAP 1.2 address.
      Show
      Previously, when <literal>jbossws.undefined.host</literal> was used as the value of the <systemitem>webServiceHost</systemitem> property in the <filename>jboss-beans.xml</filename> file, the <literal>REPLACE_WITH_ACTUAL_URL</literal> string was not replaced by the actual address when used in a WSDL definition as the value of the <systemitem>location</systemitem> attribute of the <systemitem>soap12.address</systemitem> element. This update fixes this issue and the <literal>REPLACE_WITH_ACTUAL_URL</literal> string is now replaced with the appropriate SOAP 1.2 address.
    • Release Notes Docs Status:
      Documented as Resolved Issue
    • Docs QE Status:
      NEW

      Description

      This is the fix for: https://issues.apache.org/jira/browse/CXF-3584

      The rewrite for the address occurs in updateDoc but the code (WSDLQueryHandler.java) there is only checking for the soap:address element within the 1.1 namespace and no checking 1.2 namespace.

      for (Element el : elementList) {
                              String name = el.getAttribute("name");
                              if (name.equals(ei.getName().getLocalPart())) {
                               Element soapAddress = DOMUtils.findAllElementsByTagNameNS(el,"http://schemas.xmlsoap.org/wsdl/soap/","address").iterator().next();
                               soapAddress.setAttribute("location", base);
                              }
                          }
      

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  rdickens Russell Dickenson
                  Reporter:
                  mmusaji Mustafa Musaji
                  Writer:
                  Petr Penicka
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  4 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: