2 Replies Latest reply on Aug 26, 2019 4:51 AM by Alessio Soldano

    Exposing SOAP bug on 17.0.1 Final?

    Rafael Alcaide Newbie

      Hi,

      I'm migrating a SOAP service from 11.0.0 Final, and I've faced one trouble but I don't know if it's a bug or something changed. I'd looked for it but didn't found nothing about.

       

      Usually, for remote access, we simply start the server with "-b 0.0.0.0" option. That works fine on WildFly 11. This exposes the webservice at http://hostname:port. Yes, the hostname, not it's IP.

       

      On WildFly 17.0.1, it exposes the webservice at "http://127.0.1.1" (not 127.0.0.1).  We can read the WSDL from a web browser, but when we call it from the client, it throws an error.

       

      I had to replace the original standalone.xml config file, replacing wsdl-host and adding modify-wsdl-address:

       

      <subsystem xmlns="urn:jboss:domain:webservices:2.0">
            <wsdl-host>${jboss.bind.address:127.0.0.1}</wsdl-host>
            <endpoint-config name="Standard-Endpoint-Config" />
            <endpoint-config name="Recording-Endpoint-Config">
              <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
                <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler" />
              </pre-handler-chain>
            </endpoint-config>
            <client-config name="Standard-Client-Config" />
          </subsystem>
      

       

      With:

       

      <subsystem xmlns="urn:jboss:domain:webservices:2.0">
                  <modify-wsdl-address>true</modify-wsdl-address>
                  <wsdl-host>Host's IP</wsdl-host>
                  <endpoint-config name="Standard-Endpoint-Config"/>
                  <endpoint-config name="Recording-Endpoint-Config">
                      <pre-handler-chain name="recording-handlers" protocol-bindings="##SOAP11_HTTP ##SOAP11_HTTP_MTOM ##SOAP12_HTTP ##SOAP12_HTTP_MTOM">
                          <handler name="RecordingHandler" class="org.jboss.ws.common.invocation.RecordingServerHandler"/>
                      </pre-handler-chain>
                  </endpoint-config>
                  <client-config name="Standard-Client-Config"/>
              </subsystem>
      

       

      If <wsdl-host> is replaced with 0.0.0.0 (as the suposed -b param), it exposes at the same 127.0.1.1, so it looks like there's some bug here (or I didn't notice some new changes since 11.0.0).