From dev-return-13616-apmail-ws-dev-archive=ws.apache.org@ws.apache.org Wed Aug 22 16:34:03 2012 Return-Path: X-Original-To: apmail-ws-dev-archive@www.apache.org Delivered-To: apmail-ws-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 D106CD4F5 for ; Wed, 22 Aug 2012 16:34:03 +0000 (UTC) Received: (qmail 44879 invoked by uid 500); 22 Aug 2012 16:34:03 -0000 Delivered-To: apmail-ws-dev-archive@ws.apache.org Received: (qmail 44527 invoked by uid 500); 22 Aug 2012 16:34:02 -0000 Mailing-List: contact dev-help@ws.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ws.apache.org Delivered-To: mailing list dev@ws.apache.org Received: (qmail 44520 invoked by uid 99); 22 Aug 2012 16:34:02 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 16:34:02 +0000 X-ASF-Spam-Status: No, hits=2.9 required=5.0 tests=HTML_MESSAGE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [64.85.173.253] (HELO server.dankulp.com) (64.85.173.253) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 22 Aug 2012 16:33:55 +0000 Received: by server.dankulp.com (Postfix, from userid 5000) id 5E6E6182B7E; Wed, 22 Aug 2012 12:33:34 -0400 (EDT) X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on server.dankulp.com X-Spam-Level: X-Msg-File: /tmp/mailfilter-dev@ws.apache.org.wJJq67EnKx Received: from macbook.house.dankulp.com (c-24-91-72-253.hsd1.ma.comcast.net [24.91.72.253]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by server.dankulp.com (Postfix) with ESMTPSA id 21EAE1829D1; Wed, 22 Aug 2012 12:33:33 -0400 (EDT) From: Daniel Kulp Content-Type: multipart/alternative; boundary="Apple-Mail=_8A2FA0C7-8ABA-4702-BBF3-9948C66949ED" Message-Id: <5C012363-D7BD-46B6-B4FD-5C74B4B733BB@apache.org> Mime-Version: 1.0 (Mac OS X Mail 6.0 \(1485\)) Subject: Re: WSS4J 2.0 package names Date: Wed, 22 Aug 2012 12:33:32 -0400 References: To: dev@ws.apache.org, coheigea@apache.org In-Reply-To: X-Mailer: Apple Mail (2.1485) X-Old-Spam-Status: No, score=-102.9 required=3.0 tests=ALL_TRUSTED,BAYES_00, SHORTCIRCUIT shortcircuit=ham autolearn=disabled version=3.3.2 --Apple-Mail=_8A2FA0C7-8ABA-4702-BBF3-9948C66949ED Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On Aug 21, 2012, at 10:35 AM, Colm O hEigeartaigh = wrote: > Hi all, >=20 > WSS4J trunk now has the following modules and package names: >=20 > parent > bindings -> org.apache.ws.security.binding.* > policy -> org.apache.ws.security.policy.* > ws-security-common -> org.apache.ws.security.common.* > ws-security-dom -> org.apache.ws.security.dom.* > ws-security-stax -> org.apache.ws.security.stax.* > ws-security-policy-stax -> org.apache.ws.security.policy.stax.* >=20 > They will probably undergo a few more changes before the release. = Should we move to use org.apache.wss4j instead of org.apache.ws.security = as suggested by Andreas here: >=20 > https://issues.apache.org/jira/browse/WSS-350 If we changed the package names, that should allow WSS4J 2.0 and 1.6 to = co-exist, right? Thus, things like CXF could keep the 1.6 based code = around for a release or so while users migrate. If that's the case, = I'd support it. :-) --=20 Daniel Kulp dkulp@apache.org - http://dankulp.com/blog Talend Community Coder - http://coders.talend.com --Apple-Mail=_8A2FA0C7-8ABA-4702-BBF3-9948C66949ED Content-Transfer-Encoding: 7bit Content-Type: text/html; charset=iso-8859-1
On Aug 21, 2012, at 10:35 AM, Colm O hEigeartaigh <coheigea@apache.org> wrote:

Hi all,

WSS4J trunk now has the following modules and package names:

parent
bindings -> org.apache.ws.security.binding.*
policy -> org.apache.ws.security.policy.*
ws-security-common -> org.apache.ws.security.common.*
ws-security-dom -> org.apache.ws.security.dom.*
ws-security-stax -> org.apache.ws.security.stax.*
ws-security-policy-stax -> org.apache.ws.security.policy.stax.*

They will probably undergo a few more changes before the release. Should we move to use org.apache.wss4j instead of org.apache.ws.security as suggested by Andreas here:

https://issues.apache.org/jira/browse/WSS-350

If we changed the package names, that should allow WSS4J 2.0 and 1.6 to co-exist, right?   Thus, things like CXF could keep the 1.6 based code around for a release or so while users migrate.   If that's the case, I'd support it.  :-)


-- 
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

--Apple-Mail=_8A2FA0C7-8ABA-4702-BBF3-9948C66949ED--