On Thursday, August 18, 2011 2:05:45 PM jaybytez wrote: > We are using CXF 2.2.12 (upgrading to 2.4.1) on WLS 11. > > The interesting thing is that we don't specifically gen the wsdl when a > ?wsdl request comes in, CXF is fulfilling that. > > If we hit the WLS instance directly over http, then the WSDL soap:address is > set to the WLS instance with a protocol of http. > > If we hit the VIP (via a DNS name) fronting the Apache/WLS instance directly > over https, then the WSDL soap:address is set to the DNS name with a > protocol of http. > > How does CXF/WLS determine to resolve the soap:address that it provides in > the WSDL?
It pretty much just uses the information that the Servlet container provides us. If a frontend proxy thing forwards the https request internally over an http connection, the Servlet may be just recording it as http. With the more recent versions of CXF, you can set a property on the endpoint of: publishedEndpointUrl with the value that you want always stuck in the address. > Does it cause a problem doing a web service invocation over https if the > soap:address is set to http? > > Thanks for the continued help...jay > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/SSL-and-the-soap-address-showing-http-tp471 > 3432p4713432.html Sent from the cxf-user mailing list archive at Nabble.com. -- Daniel Kulp [email protected] http://dankulp.com/blog Talend - http://www.talend.com
