On Tuesday 17 August 2010 3:12:31 pm Glen Mazza wrote: > Thanks Dan. But to generalize what you're saying, the BindingProvider.XXXX > properties (not just endpoint URL but also basic auth username & password) > are meant to be programmatically set and *not* done via the cxf.xml file, > correct? (Even though there are some values that can be informally used, > such as the one you're giving below) That's why they're not defined here in > cxf.xml configuration: > > https://cwiki.apache.org/confluence/display/CXF20DOC/Client+HTTP+Transport+ > %28including+SSL+support%29 > > Am I correct in that sense?
Possibly. I'm not 100% sure. :-) When you use the programmatic stuff, the getRequestContext() call returns a map that maps the passed in keys into the appropriate keys needed for CXF. Thus, the BindingProvider.ENDPOINT_ADDRESS thing really ends up setting the org.apache.cxf.request.uri property which is what the HTTP transport would be looking for. What I DON'T know (would need to try) is if properties mapped in via the jaxws:properties thing also end up getting mapped. I THINK it does as jaxws:endpoint is a wrapper to our EndpointImpl which I think does wrap things set on it. However, I'm not 100% sure. Dan > > Thanks, > Glen > > Daniel Kulp wrote: > > No, the "Host"property is just the value stuck in the Host HTTP header. > > Not > > needed 99% of the time (or more). > > > > In general, you can set the endpoint property of > > > > org.apache.cxf.request.uri > > > > to the URL you want to hit using the jaxws:properties child element of > > jaxws:client. I believe that will work. Not 100% sure though. -- Daniel Kulp [email protected] http://dankulp.com/blog
