If CXF is ignoring BindingProvider.ENDPOINT_ADDRESS_PROPERTY, then yes, that's a bug. Please submit a JIRA for it.
Glen Christopher Cheng wrote: > > It's probably a bug in version 2.1.3 > > <snip/> > > The following is from HTTPConduit. If defaultEndpointURL is not null, it > will not use the new URL in BindingProvider.ENDPOINT_ADDRESS_PROPERTY. > Therefore, the only way is to change defaultEndpointURL in WSDL which is > not > user friendly. Could this be improved in version 2.1.4? > -- View this message in context: http://www.nabble.com/Re%3A-Re%3A-problem-changing-endpoint-address-from-https-to-http-tp21254391p21321326.html Sent from the cxf-user mailing list archive at Nabble.com.
