Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@cxf.apache.org
Date: Wed, 24 Jun 2015 05:56:33 -0700 (MST)
From: Andrew <Andrei.Diaconu@booxware.de>
To: users@cxf.apache.org
Message-ID: <1435150593629-5758553.post@n5.nabble.com>
In-Reply-To: 
 <CAB8XdGAYPx72GdpLHtZ1_9ojcyVanmB34EeZhV5uNJeeVHxx+Q@mail.gmail.com>
References: <1434806070805-5758451.post@n5.nabble.com>
 <CAB8XdGAYPx72GdpLHtZ1_9ojcyVanmB34EeZhV5uNJeeVHxx+Q@mail.gmail.com>
Subject: Re: Caching and reusing SecureConversationToken - how?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

coheigea wrote
> What does your client code look like? Caching only works for the same
> client proxy. If you are closing the proxy, or else creating a new one,
> then the cached SecurityContextToken will not be retrieved. If you are
> re-using the same client proxy, then the SecurityContextToken should be
> retrieved from the cache + re-used.
> 
> Colm.

Right you are. My client is WSDL-first and uses the Java classes generated
per the WSDL to get a new Proxy before each call. I changed it just now to
reuse one and the same proxy for multiple requests, and the issued security
token does indeed get reused.

This is by design, right? Would it make sense / be possible for the same
security token to be (re)used by distinct client proxy objects?

In any event, I think my question is answered. Thanks!


--
View this message in context: http://cxf.547215.n5.nabble.com/Caching-and-reusing-SecureConversationToken-how-tp5758451p5758553.html
Sent from the cxf-user mailing list archive at Nabble.com.