And also the same issue applies to username/password properties.
Jarek On 4/17/07, Daniel Kulp <[EMAIL PROTECTED]> wrote:
I think the problem is that someplace, we're clearing the request context between invocations. Thus, the ENDPOINT_ADDRESS_PROPERTY is being cleared out of there and is then not available for future calls. If we didn't clear it, then it would still be there and we wouldn't need the to make it "permanent" at the EndpointInfo level. I'll try and dig around a bit tomorrow and figure out where we're clearing that. Just FYI: the response context gets cleared, the request context does not. Section 4.2.1 of jaxws spec. Dan On Tuesday 17 April 2007 17:14, Jarek Gawor wrote: > Hi, > > Regarding https://issues.apache.org/jira/browse/CXF-414 issue. What I > actually meant and expected to see when I set the endpoint address > property on the proxy, is that the address set will be used for all > calls made using that proxy (unless of course is re-set again). For > example: > > Greeter g = foo.getPort(Greeter.class); > (javax.xml.ws.BindingProvider)g).getRequestContext().put(javax.xml.ws. >BindingProvider.ENDPOINT_ADDRESS_PROPERTY, "http://foo/bar";); > > // call 1 > g.helloFoo(); > > // call 2 > g.helloBar(); > > For both calls address of "http://foo/bar"; will be used. It looks like > the endpoint address property is currently lost on the second call > right now. > > Jarek -- J. Daniel Kulp Principal Engineer IONA P: 781-902-8727 C: 508-380-7194 [EMAIL PROTECTED] http://www.dankulp.com/blog
