Created attachment 589169 [details] wsAdapter.esb Description of problem: Unable to expose JBoss ESB as webservice using SOAP over HTTPs Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1.add the below content to server.xml ================================================================== <Connector port="8443" protocol="HTTP/1.1" SSLEnabled="true" maxThreads="150" scheme="https" secure="true" clientAuth="false" sslProtocol="TLS" keyAlias="webservice_proxy_security" keystoreFile="D:/JBossLab/Jboss_SOA_1/jboss-soa-p-5/jboss-as/samples/quickstarts/webservice_proxy_security/build/webservice_proxy_security.keystore" keystorePass="webservice_proxy_security_pass" truststoreFile="D:/JBossLab/Jboss_SOA_1/jboss-soa-p-5/jboss-as/samples/quickstarts/webservice_proxy_security/build/webservice_proxy_security.keystore" truststorePass="webservice_proxy_security_pass" /> <Engine name="jboss.web" defaultHost="localhost"> ====================================================================== Or replace the server.xml in '\jboss-soa-p-5\jboss-as\server\default\deploy\jbossweb.sar' with the attached one. 2.Deploy the attached esb file 3. check the wsdl created in jboss-soa-p-5\jboss-as\server\default\data\wsdl\wsAdapter Actual results: The end point is shown like http://localhost:8080/wsAdapter/ebws/webServiceConsumeCat1/webServiceConsume1 Expected results: The end point to be created on The end point is shown like https://localhost:8443/wsAdapter/ebws/webServiceConsumeCat1/webServiceConsume1 Additional info:
Created attachment 589171 [details] server.xml
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.