2 Replies Latest reply on Jun 2, 2010 12:34 PM by David Ward

    How to Control URL's in JBoss ESB WSDL's

    Nick Newman Newbie

      Hi,

       

      I'm just starting to look at JBoss ESB and have deployed its quickstart "publish_as_webservice" and things work.

       

      But now I want to access the ESB via a front-end proxy (e.g. a load balancer).  How can I tell the ESB to use the front-end machine name and port in its WSDL?  It needs to be there both for the included schema URL's and for the service end-point URL.

       

      Many thanks,

      Nick

        • 1. Re: How to Control URL's in JBoss ESB WSDL's
          Nick Newman Newbie

          Hmmm.  No answers.   Yet it seems that this is fundamental, since if the back-end addresses are being put into the WSDL, and if the back-end is not visible to the client, then automated tools (e.g. SOAP-UI) will not work correctly.

           

          Fortunately I found what I believe to be the answer in a post to the Web Services community:  https://community.jboss.org/message/524256

           

          In the 6th entry there (from Robert Crank) he directs us to jboss-beans.xml.  That file contains the address and port to use when re-writing the address to use.  Setting these values causes them to be used in both schema-location references and in the endpoint location, as required.

           

          With that fix all is well in the world again ;-)

           

          Nick

          • 2. Re: How to Control URL's in JBoss ESB WSDL's
            David Ward Master

            Hmmm.  The SOAPProxy action, when it creates WSDL for itself, will respect these properties:

            • org.jboss.soa.esb.http.host
            • org.jboss.soa.esb.http.port
            • org.jboss.soa.esb.http.securePort

            if defined in your server's deploy/jbossesb.sar/jbossesb-properties.xml file, in the "transports" section.  The WSDL will then have all it's soap:address locations transformed to use the specified host and/or ports.

             

            If you are not satisfied with the solution you found, and would like the above capability to be extended to other ESB-generated WSDL's, please feel free to add a Jira Feature Request (or maybe this could be viewed as a Bug...) here:

            https://jira.jboss.org/browse/JBESB

             

            Best regards,

            David