1 2 Previous Next 17 Replies Latest reply on Mar 15, 2006 1:02 PM by catfishtyphoon Go to original post
      • 15. Re: making a redeployable .war or .ear
        darickard
        darickard Jun 20, 2005 8:05 PM (in response to chriscorbell)

        After restarting JBoss, this exception did not recur. So, the solution appears to be to modify the WSDL to contain a valid URL (I couldn't get wscompile to do this, I had to use the replaceregexp Ant task), then change the AlwaysModifySOAPAddress attribute to false for the AxisService mbean in deploy\jboss-ws4ee.sar\META-INF\jboss-service.xml.

        Thanks for everyone's help!

          • Actions
        • 16. Re: making a redeployable .war or .ear
          catfishtyphoon Mar 15, 2006 12:20 PM (in response to chriscorbell)

          I'm not finding this in 4.0.3. The problem seems to be that my web service URL is getting rewritten. I ask for

          https://blah.internap.com:8443/test-service/Echo?wsdl

          but later in the SOAP call I see: 
          DEBUG org.jboss.axis.transport.http.HTTPSender - TargetURL: http://blah.internap.com:8080/test-service/Echo
 [java] 3281 [main] DEBUG org.jboss.axis.transport.http.HTTPSender - Connection refused

          Because we have blocked 8080 to all but localhost.
          I have the 
          https://SOME_URL_TO_BE_REPLACED_BY_JBOSS

          line in my wsdl file, so I assume this is getting rewritten by JBoss, which is good because I don't know the deployment host at compile time. But how do I tell it to redirect to the https address (WebServiceSecurePort) and not to the WebServicePort?

            • Actions
          • 17. Re: making a redeployable .war or .ear
            catfishtyphoon Mar 15, 2006 1:02 PM (in response to chriscorbell)

            So, I was platying around with it, and I find that making the line in the wsdl to be:

            https://SOME_URL_TO_BE_REPLACED_BY_JBOSS:8443

            works, but this does not seem like the right way to do it at all. If the server config changes to move WebServiceSecurePort to a different port, then I have to recompile all my WAR files with the new port number. Shouldn't I be able to configure it to bind to the secure port in the xml? Isn't the web service endpoint, as someone mentioned earlier in this post, bound to the service rather than a port per se?

              • Actions
            1 2 Previous Next