Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Received-SPF: pass (athena.apache.org: domain of willem.jiang@gmail.com
 designates 209.85.213.169 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:content-type:content-transfer-encoding;
        b=StgLAPwmMinp4WJBIIQgcqozAuePGwpTbsvqu5MhU+Njm/z9PoNizCo6ZBX98IrkEj
         37Hk9xWXs1r3xxFy3UQFYhTaHHUVGaVpY2PwZGRL7OSnY6ll+ipt8R/IHKsUyjGSWfJl
         E4mRtk+11sQQecII/1r5fZ2GI6XKJkvTkPU54=
Message-ID: <4D2C5552.7040306@gmail.com>
Date: Tue, 11 Jan 2011 21:04:18 +0800
From: Willem Jiang <willem.jiang@gmail.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US;
 rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: users@cxf.apache.org
Subject: Re: Effect of an SSL-terminating proxy on autoRewriteSoapAddress
References: <4D2B73D8.6050008@spudsoft.co.uk> <4D2BCA40.30501@gmail.com>
 <20110111084858.40261b4040lyx7c0@91.84.217.110>
In-Reply-To: <20110111084858.40261b4040lyx7c0@91.84.217.110>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

On 1/11/11 4:48 PM, Jim Talbut wrote:
> Willem,
>
> Quoting Willem Jiang <willem.jiang@gmail.com>:
>> On 1/11/11 5:02 AM, Jim Talbut wrote:
>>> I can't see any standard way for a java servlet to know that the
>>> original request was over https - given that the request it sees isn't.
>>> Our load balancer does add a few HTTP headers to the request, so if I
>>> could hook the WSDL response with my own code I could set the location
>>> correctly - but is that possible?
>>
>> I think you can interceptor the WSDL query request in your load
>> balancer instead of delegate that request to CXF endpoints.
>> In this way, you can get the full control of the WSDL port address.
>> The only short coming I can see is you need to take care of the
>> services WSDL in you code.
> Unfortunately the load balancer is a hardware device, we have no ability
> to run our code on it :(.
>
>>> I think I'm stuck with declaring two CXF endpoints, an external one with
>>> a published URL and an internal one with autoRewriteSoapAddress.
>>> Anyone got any better ideas?
>> I don't think current CXF supports two address as you want.
> That surprises me.
> Can I not have (in spring) two jaxws:endpoint elements with the same
> implementor attribute?
>
Oh, my bad. I misunderstand your meaning.
You can do that, but you need to make sure your implementer is 
multi-thread safe.

> Jim
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
>
>


-- 
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog:    http://willemjiang.blogspot.com (English)
          http://jnn.javaeye.com (Chinese)
Twitter: willemjiang