Thanks for the suggestion. We had the opportunity to test out the suggestion, but it is
still setting the SOAP address location to be HTTP instead of HTTPS.
We made the web.xml changes as described in the Wiki link -- this had no discernible
impact on the generated SOAP address location in the WSDL. It still uses a regular HTTP
address when generating the service URL.
We did confirm that the new web.xml was being deployed, as this file was made available
through the temporary expansion of the EAR file created when deploying the web service.
Despite the change, we are still seeing an HTTP address being generated.
Are there any other SSL configuration resources available that discuss this issue?
We've scoured most of the web resources and haven't found anything, but are
curious to see if there's anything else that may be helpful.
--Rich.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4203664#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...