Return-Path: X-Original-To: apmail-cxf-dev-archive@www.apache.org Delivered-To: apmail-cxf-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id C3495CAE6 for ; Wed, 8 Aug 2012 08:32:42 +0000 (UTC) Received: (qmail 39903 invoked by uid 500); 8 Aug 2012 08:32:41 -0000 Delivered-To: apmail-cxf-dev-archive@cxf.apache.org Received: (qmail 39596 invoked by uid 500); 8 Aug 2012 08:32:35 -0000 Mailing-List: contact dev-help@cxf.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cxf.apache.org Delivered-To: mailing list dev@cxf.apache.org Received: (qmail 39531 invoked by uid 99); 8 Aug 2012 08:32:33 -0000 Received: from minotaur.apache.org (HELO minotaur.apache.org) (140.211.11.9) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2012 08:32:33 +0000 Received: from localhost (HELO mail-lpp01m010-f41.google.com) (127.0.0.1) (smtp-auth username coheigea, mechanism plain) by minotaur.apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Aug 2012 08:32:32 +0000 Received: by lahd3 with SMTP id d3so262034lah.0 for ; Wed, 08 Aug 2012 01:32:31 -0700 (PDT) MIME-Version: 1.0 Received: by 10.112.11.38 with SMTP id n6mr7267171lbb.82.1344414750986; Wed, 08 Aug 2012 01:32:30 -0700 (PDT) Reply-To: coheigea@apache.org Received: by 10.112.41.100 with HTTP; Wed, 8 Aug 2012 01:32:30 -0700 (PDT) In-Reply-To: <1D4606F4-5E87-4291-A37D-2BEDF49619DA@gmail.com> References: <1D4606F4-5E87-4291-A37D-2BEDF49619DA@gmail.com> Date: Wed, 8 Aug 2012 09:32:30 +0100 Message-ID: Subject: Re: WS-Security interopfest examples From: Colm O hEigeartaigh To: Freeman Fang Cc: dev@cxf.apache.org Content-Type: multipart/alternative; boundary=e0cb4efe326ca9d19c04c6bcf301 --e0cb4efe326ca9d19c04c6bcf301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Ok with no objections I'm going to remove the WS-Security interopfest code from examples on trunk. Colm. On Wed, Aug 8, 2012 at 4:02 AM, Freeman Fang wrote= : > =EF=BC=8B1 > Freeman > > =EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D= =EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D=EF=BC=8D > Freeman Fang > > FuseSource > Email:ffang@fusesource.com > Web: fusesource.com > Twitter: freemanfang > Blog: http://freemanfang.blogspot.com > http://blog.sina.com.cn/u/1473905042 > weibo: http://weibo.com/u/1473905042 > > On 2012-8-3, at =E4=B8=8B=E5=8D=889:18, Colm O hEigeartaigh wrote: > > Hi all, > > We previously discussed what to do with the WS-Security interopfest > examples here: > > > http://cxf.547215.n5.nabble.com/DISCUSS-how-to-handle-ws-security-interop= fest-example-td4805281.html > > http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/samp= les/ws_security/interopfest/ > > I propose to just nuke these examples, as the policies are (or should be, > I'll do a quick check) covered already in the WS-Security and STS system > tests already. > > Any objections? > > Colm. > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com > > > --=20 Colm O hEigeartaigh Talend Community Coder http://coders.talend.com --e0cb4efe326ca9d19c04c6bcf301--