On Tuesday 06 January 2009 6:06:01 pm Glen Mazza wrote: > If CXF is ignoring BindingProvider.ENDPOINT_ADDRESS_PROPERTY, then yes, > that's a bug. Please submit a JIRA for it.
CXF isn't "ignoreing" the ENDPOINT_ADDRESS_PROPERTY. However, CXF doesn't allow changing protocols via the ENDPOINT_ADDRESS_PROPERTY. You cannot change from HTTP -> JMS for example via setting that property. Right now, CXF considers a change from HTTP -> HTTPS (and vice versa) a protocol change. Fixing the HTTP -> JMS thing would be quite a bit of work as that involves an interceptor very early in the chain that would completely swap out the conduit. Fixing http <---> https is a quit bit easier, in a semi-hackish way. Testing a fix now. If the ENDPOINT_ADDRESS_PROPERTY is set, I can just wipe out the connectionFactory and re-acquire it. Not ideal, but a temporary fix. Dan > > 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? -- Daniel Kulp [email protected] http://dankulp.com/blog
