I'll probably have some time to think about this in the next weeks, sorry. Generally speaking I'd really much appreciate a patch in this area; this quite a complex topic, as there're really many different user conditions here, requiring a different behaviour of the stack. Please try running the whole jbossws testsuite once you have the patch, as I recently revisited it to try covering all the usecase we've dealt with regarding soap address rewrite needs.

Thanks

Have you seen this, maybe it will help

jbossws.deployer/META-INF/jboss-beans.xml

<bean name="ServiceEndpointManager" class="org.jboss.ws.server.ServiceEndpointManager">
      <!--
        The WSDL, that is a required deployment artifact for an endpoint, has a <soap:address>
        element which points to the location of the endpoint. JBoss supports rewriting of that SOAP address.
     
        If the content of <soap:address> is a valid URL, JBossWS will not rewrite it unless AlwaysModifySOAPAddress is true.
        If the content of <soap:address> is not a valid URL, JBossWS will rewrite it using the attribute values given below.
      -->
      <property name="webServiceHost">${jboss.bind.address}</property>
      <property name="webServiceSecurePort">8443</property>
      <property name="webServicePort">8080</property>
      <property name="alwaysModifySOAPAddress">true</property>
      ...
    </bean>

Did anyone ever find a way to do this? I have an almost identical situation.

Ulrich Romahn wrote:

 

So, we have multiple options to configure the generation of the service URL:

1. we configure it statically by setting "webServiceHost" to our public server name, or
2. we configure it using dynamic rewrite based on the request URL

 

If we use option #1, JBoss will always generate a service URL with "http" no matter what else we do

Generally speaking, something you can do is provide the wsdl you want to be exposed in your deployment. First you deploy without it, then you save the generated wsdl, modify it as you wish, add it and reference it (@WebService(wsdlLocation = "WEB-INF/...")) in your deployment and finally re-deploy.

Something else you might want to try is setting your soap:address to something like "https://REPLACE-ME", that should force the https protocol to be use in the soap:address when rewriting it. I think this probably has the side effect of overwriting the webServicePort you might want to specify though.

If nothing of this helps, please create a feature request jira. We might think about adding another configuration option (webServiceProtocol) and achieve what you want throught that.

Can anyone help with this.  I am able to replace the WSDL and successfully having it show https, however, clients are getting an exception :

"Endpoint not found"

I guess Robert Crank's hint was the good one. I had situation when there was always localhost in soap adress. To solve this I just commented these two lines out (in document jbossws.deployer/META-INF/jboss-beans.xml):

<property name="webServiceHost">${jboss.bind.address}</property>
<property name="modifySOAPAddress">true</property>

jbossws.deployer/META-INF/jboss-beans.xml exists only in jboss5.1/server/all and not the configuration used  ?!

do it like a servlet. with a "class xxxxxx implements Provider<SOAPMessage>"

I managed to follow this advice in a simila situation successfully. See also my additional related questions in https://community.jboss.org/thread/205925

I am having the same problem with the soap address location having http in the wsdl url instead https.

Any help and solution regarding this will be really appreciated.

Thanks in advance.