Return-Path: 
 <users-return-36759-apmail-cxf-users-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-users-archive@www.apache.org
Delivered-To: apmail-cxf-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 3970DD004
	for <apmail-cxf-users-archive@www.apache.org>;
 Mon, 15 Oct 2012 16:41:57 +0000 (UTC)
Received: (qmail 39589 invoked by uid 500); 15 Oct 2012 16:41:56 -0000
Delivered-To: apmail-cxf-users-archive@cxf.apache.org
Received: (qmail 39544 invoked by uid 500); 15 Oct 2012 16:41:56 -0000
Mailing-List: contact users-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@cxf.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@cxf.apache.org>
List-Post: <mailto:users@cxf.apache.org>
List-Id: <users.cxf.apache.org>
Reply-To: users@cxf.apache.org
Delivered-To: mailing list users@cxf.apache.org
Received: (qmail 39536 invoked by uid 99); 15 Oct 2012 16:41:56 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 16:41:56 +0000
X-ASF-Spam-Status: No, hits=2.2 required=5.0
	tests=FREEMAIL_ENVFROM_END_DIGIT,SPF_NEUTRAL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of ginachoi88@gmail.com)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Oct 2012 16:41:49 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <ginachoi88@gmail.com>)
	id 1TNnjN-0005JF-4l
	for users@cxf.apache.org; Mon, 15 Oct 2012 09:41:29 -0700
Date: Mon, 15 Oct 2012 09:41:29 -0700 (PDT)
From: Gina Choi <ginachoi88@gmail.com>
To: users@cxf.apache.org
Message-ID: <1350319289138-5716675.post@n5.nabble.com>
In-Reply-To: <61585B70-DA3A-4398-9041-70FC83359577@apache.org>
References: <1350054261011-5716524.post@n5.nabble.com>
 <1350307933928-5716650.post@n5.nabble.com>
 <61585B70-DA3A-4398-9041-70FC83359577@apache.org>
Subject: Re: Fediz(SSO) - Do we need to unset token?
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Hi Dan,

Thanks for your response. If we look at
org.apache.cxf.fediz.example.SecurityTokenThreadLocal.java class, I only see
get and set method. I could directly call TLS.remove() to unset the token,
but should we have a remove method inside SecurityTokenThreadLocal.java
class?


public final class SecurityTokenThreadLocal {

    private static final ThreadLocal<Element> TLS = 
        new ThreadLocal<Element>() {
        };

    private SecurityTokenThreadLocal() {
    }    
        
    public static void setToken(Element token) {
        TLS.set(token);
    }

    public static Element getToken() {
        return TLS.get();
    }
    

}

Gina



--
View this message in context: http://cxf.547215.n5.nabble.com/Fediz-SSO-Do-we-need-to-unset-token-tp5716524p5716675.html
Sent from the cxf-user mailing list archive at Nabble.com.