cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor" <jga...@gmail.com>
Subject Re: Service address in WSDL and EPR
Date Thu, 18 Sep 2008 18:49:02 GMT
On Wed, Sep 17, 2008 at 3:39 PM, Daniel Kulp <dkulp@apache.org> wrote:
> On Wednesday 17 September 2008 3:28:13 pm Jarek Gawor wrote:
>> Hi,
>>
>> I was working in Geronimo on a simple issue where the service endpoint
>> url address in WSDL gets cached on the very first request and does not
>> get updated. I was looking through similar code in CXF and noticed a
>> few things and now I'm wondering how things should work.
>>
>> 1) What's the purpose of publishedEndpointUrl property? I see that it
>> can be set in EndpointImpl and it is used in WSDLQueryHandler to
>> update the service soap:address location. But, a) shouldn't this
>> property be also used to update the schema/wsdl imports? and b)
>> shouldn't that value also be returned in
>> WebServiceContext.getEndpointReference() and/or
>> Endpoint.getEndpointReference()?
>
> It's to workaround issues with various proxy servers and load balancers that
> don't properly send a "Host" variable or the proxy is on a different port
> than the real.    In those cases, the updated URL would not properly reflect
> the "public" URL that is really being exposed to the internet.  The
> publishedEndpointUrl kind of allows overriding the serlvet container provided
> information with the real information that the public would know about.

Ok, that's what I thought. So, once set, the publishedEndpointUrl
property should be returned in the EPR and the schema/wsdl imports.

Jarek

Mime
View raw message