You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Colm O hEigeartaigh <co...@apache.org> on 2012/08/21 16:35:43 UTC

WSS4J 2.0 package names

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

?

Colm.


-- 
Colm O hEigeartaigh

Talend Community Coder
http://coders.talend.com

Re: WSS4J 2.0 package names

Posted by Daniel Kulp <dk...@apache.org>.
On Aug 21, 2012, at 10:35 AM, Colm O hEigeartaigh <co...@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

Re: WSS4J 2.0 package names

Posted by Sagara Gunathunga <sa...@gmail.com>.
+1 to change package names. In Axis2 context co-existence of WSS4J 2.0
and 1.6 is very helpful feature for us.

Thanks !

On Tue, Aug 21, 2012 at 8:05 PM, Colm O hEigeartaigh
<co...@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
>
> ?
>
> Colm.
>
>
> --
> Colm O hEigeartaigh
>
> Talend Community Coder
> http://coders.talend.com
>



-- 
Sagara Gunathunga

Blog      - http://ssagara.blogspot.com
Web      - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org