You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by Isuru Suriarachchi <is...@gmail.com> on 2009/02/17 12:50:29 UTC

Axiom based XML Security Implementation

Hi all,

As we all know there are some performance issues with Rampart as the
security module for Axis2. The main cause of this issue is the usage of DOM
in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
http://santuario.apache.org/index.html) on which Rampart is written.
Therefore as a research project, four of us (Sameera Jayasoma, Saliya
Ekanayake, Kalani Ruwanpathirana and myself) have implemented a WS-Security
implementation totally on Axiom. It consists of two layers and the bottom
layer handles the xml security stuff. So we thought of adding this Axiom
based xml securiy implementation as a new ws-commons project.

Saliya has already created a jira at
https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code is
attached to the jira. This code is already tested and provides the same
functionality as xmlsec with better performance.

We have decided to use the name "thomara" for this and I'm planning to
commit this code at
https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara.
Comments please?..

Thanks,
Isuru

Re: Axiom based XML Security Implementation

Posted by David Illsley <da...@gmail.com>.
On Wed, Feb 18, 2009 at 5:25 AM, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi David,
>
> On Tue, Feb 17, 2009 at 11:33 PM, David Illsley <da...@gmail.com>wrote:
>
>> Great to have this code... I have a couple of thoughts...
>>
>> Firstly, where was this code developed? It looks like a bulk
>> contribution to me, so I suspect it should really go through the IP
>> clearance process [1]
>
>
> As Saliya said this was our final year project at the university. There are
> only four contributors. Saliya, Sameera, Kalani and my self. Should it still
> go through this IP clearance process?

4 Contributors, quite a few classes (though no unit tests?)... to me
that's probably a 'substantial contribution that was not developed
within the ASF's source control system and on our public mailing
lists' so yes, I think we probably should go through that process.

David

Re: Axiom based XML Security Implementation

Posted by Isuru Suriarachchi <is...@gmail.com>.
Hi David,

On Tue, Feb 17, 2009 at 11:33 PM, David Illsley <da...@gmail.com>wrote:

> Great to have this code... I have a couple of thoughts...
>
> Firstly, where was this code developed? It looks like a bulk
> contribution to me, so I suspect it should really go through the IP
> clearance process [1]


As Saliya said this was our final year project at the university. There are
only four contributors. Saliya, Sameera, Kalani and my self. Should it still
go through this IP clearance process?

Thanks,
Isuru


>
>
> Secondly, should it really be a separate commons project? The commons
> already suffers from lots of small projects that have few committers
> and with poor visibility. I wonder if it would be better to make it
> part of Axiom and promote Axiom to be a full sub project. Thoughts?
>
> David
>
> [1] http://incubator.apache.org/ip-clearance/index.html
>



-- 
Software Engineer,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/

Re: Axiom based XML Security Implementation

Posted by Benson Margulies <bi...@gmail.com>.
I for one don't see how bloat comes into it. Nothing stops the Axiom
project from having a build that produces multiple jar files that are
loosely coupled. The discussion here is about the conceptual overhead
of formal component process.

On Wed, Feb 18, 2009 at 2:40 AM, David Illsley <da...@gmail.com> wrote:
> Thanks for the information. I'm generally unconvinced by the argument
> that having an optional 100KB axiom-xmlsecurity module counts as
> 'bloat'. To me it's better for users for it to be part of Axiom
> because information about this additional functionality that Axiom
> users may wish to use will be more obvious. From an Apache
> perspective, I think having it part of Axiom would have a couple of
> advantages...
> 1. Fewer dependency projects which need to be lined up for new
> releases of e.f. Axis2/Rampart2
> 2. Giving it a separate name encourages people to think of it as
> something separate and owned by a separate community which, given the
> size of the codebase seems unnecessary. I think it does properly
> belong as part of the Axiom community
>
> David
>
> P.S. What does 'thomara' mean and have you done the appropriate name checks?
>

Re: Axiom based XML Security Implementation

Posted by Saliya Ekanayake <es...@gmail.com>.
A small clarification on the name. See the comments inside.

On Thu, Feb 19, 2009 at 10:42 AM, Saliya Ekanayake <es...@gmail.com>wrote:

> Just a small note on the name "Thomara":
>
> In Sinhala it denotes a weapon used by King's guards in the past. The shape
> is similar to a spear (at the moment I am unable to find an image in the
> Internet). We chose the name since it relates with security and it can be
> pronounced with less effort. The "tho" is pronounced as in "thought", "ma"
> is pronounced as in "customer", and "ra" is pronounced similar to "ma".


The last two letters, i.e. "ra" is pronounced similar to the pronunciation
of "ma" except for the "m" being replaced by "r".

Thanks,
Saliya

>
>
> We initially had the idea of naming it "Paliha", which stands for shield in
> Sinhala. The only reason for not taking it was the feeling that it will be
> bit hard to pronounce. If others find that this is not the case, then we
> will be happy to consider changing it to "Paliha" as well.
>
> Thanks,
> Saliya
>
>
> On Wed, Feb 18, 2009 at 9:58 PM, Sanjiva Weerawarana <
> sanjiva@opensource.lk> wrote:
>
>> David, anyone can use Axiom as an efficient XML Infoset representation.
>> Thomara is an implementation of XML Encryption and XML Signature on top of
>> that representation + XML Canonicalization.
>>
>> Only a (small) subset of people who use Axiom would need this stuff -
>> anyone using WS-Security etc. obviously does. There is no intrinsic
>> connection to Axiom to say that it should be in the Axiom subproject of
>> commons.
>>
>> On your concern of having small projects with a small community, that's
>> *exactly* why we created commons-dev to be a common dev list for all these
>> small projects. They're small subprojects because they're independent /
>> orthogonal components which can be combined as desired.
>>
>> I have no objection to considering a move of Axiom to TLP, but that has
>> nothing to do with this project. Orthogonal conversation; let's do it
>> separately.
>>
>> AFAIK thomara has no meaning in Sinhalese but prolly my poor knowledge of
>> Sinhala will be exposed by that statement ;-).
>>
>> Sanjiva.
>>
>>
>> David Illsley wrote:
>>
>>> Thanks for the information. I'm generally unconvinced by the argument
>>> that having an optional 100KB axiom-xmlsecurity module counts as
>>> 'bloat'. To me it's better for users for it to be part of Axiom
>>> because information about this additional functionality that Axiom
>>> users may wish to use will be more obvious. From an Apache
>>> perspective, I think having it part of Axiom would have a couple of
>>> advantages...
>>> 1. Fewer dependency projects which need to be lined up for new
>>> releases of e.f. Axis2/Rampart2
>>> 2. Giving it a separate name encourages people to think of it as
>>> something separate and owned by a separate community which, given the
>>> size of the codebase seems unnecessary. I think it does properly
>>> belong as part of the Axiom community
>>>
>>> David
>>>
>>> P.S. What does 'thomara' mean and have you done the appropriate name
>>> checks?
>>>
>>
>>
>> --
>> Sanjiva Weerawarana, Ph.D.
>> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
>> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
>> Member; Apache Software Foundation; http://www.apache.org/
>> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>>
>> Blog: http://sanjiva.weerawarana.org/
>>
>
>
>
> --
> Saliya Ekanayake
> http://www.esaliya.blogspot.com
> http://www.esaliya.wordpress.com
>



-- 
Saliya Ekanayake
http://www.esaliya.blogspot.com
http://www.esaliya.wordpress.com

Re: Axiom based XML Security Implementation

Posted by Saliya Ekanayake <es...@gmail.com>.
Just a small note on the name "Thomara":

In Sinhala it denotes a weapon used by King's guards in the past. The shape
is similar to a spear (at the moment I am unable to find an image in the
Internet). We chose the name since it relates with security and it can be
pronounced with less effort. The "tho" is pronounced as in "thought", "ma"
is pronounced as in "customer", and "ra" is pronounced similar to "ma".

We initially had the idea of naming it "Paliha", which stands for shield in
Sinhala. The only reason for not taking it was the feeling that it will be
bit hard to pronounce. If others find that this is not the case, then we
will be happy to consider changing it to "Paliha" as well.

Thanks,
Saliya

On Wed, Feb 18, 2009 at 9:58 PM, Sanjiva Weerawarana
<sa...@opensource.lk>wrote:

> David, anyone can use Axiom as an efficient XML Infoset representation.
> Thomara is an implementation of XML Encryption and XML Signature on top of
> that representation + XML Canonicalization.
>
> Only a (small) subset of people who use Axiom would need this stuff -
> anyone using WS-Security etc. obviously does. There is no intrinsic
> connection to Axiom to say that it should be in the Axiom subproject of
> commons.
>
> On your concern of having small projects with a small community, that's
> *exactly* why we created commons-dev to be a common dev list for all these
> small projects. They're small subprojects because they're independent /
> orthogonal components which can be combined as desired.
>
> I have no objection to considering a move of Axiom to TLP, but that has
> nothing to do with this project. Orthogonal conversation; let's do it
> separately.
>
> AFAIK thomara has no meaning in Sinhalese but prolly my poor knowledge of
> Sinhala will be exposed by that statement ;-).
>
> Sanjiva.
>
>
> David Illsley wrote:
>
>> Thanks for the information. I'm generally unconvinced by the argument
>> that having an optional 100KB axiom-xmlsecurity module counts as
>> 'bloat'. To me it's better for users for it to be part of Axiom
>> because information about this additional functionality that Axiom
>> users may wish to use will be more obvious. From an Apache
>> perspective, I think having it part of Axiom would have a couple of
>> advantages...
>> 1. Fewer dependency projects which need to be lined up for new
>> releases of e.f. Axis2/Rampart2
>> 2. Giving it a separate name encourages people to think of it as
>> something separate and owned by a separate community which, given the
>> size of the codebase seems unnecessary. I think it does properly
>> belong as part of the Axiom community
>>
>> David
>>
>> P.S. What does 'thomara' mean and have you done the appropriate name
>> checks?
>>
>
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> Blog: http://sanjiva.weerawarana.org/
>



-- 
Saliya Ekanayake
http://www.esaliya.blogspot.com
http://www.esaliya.wordpress.com

Re: Axiom based XML Security Implementation

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
David, anyone can use Axiom as an efficient XML Infoset representation. 
Thomara is an implementation of XML Encryption and XML Signature on top of 
that representation + XML Canonicalization.

Only a (small) subset of people who use Axiom would need this stuff - 
anyone using WS-Security etc. obviously does. There is no intrinsic 
connection to Axiom to say that it should be in the Axiom subproject of 
commons.

On your concern of having small projects with a small community, that's 
*exactly* why we created commons-dev to be a common dev list for all these 
small projects. They're small subprojects because they're independent / 
orthogonal components which can be combined as desired.

I have no objection to considering a move of Axiom to TLP, but that has 
nothing to do with this project. Orthogonal conversation; let's do it 
separately.

AFAIK thomara has no meaning in Sinhalese but prolly my poor knowledge of 
Sinhala will be exposed by that statement ;-).

Sanjiva.

David Illsley wrote:
> Thanks for the information. I'm generally unconvinced by the argument
> that having an optional 100KB axiom-xmlsecurity module counts as
> 'bloat'. To me it's better for users for it to be part of Axiom
> because information about this additional functionality that Axiom
> users may wish to use will be more obvious. From an Apache
> perspective, I think having it part of Axiom would have a couple of
> advantages...
> 1. Fewer dependency projects which need to be lined up for new
> releases of e.f. Axis2/Rampart2
> 2. Giving it a separate name encourages people to think of it as
> something separate and owned by a separate community which, given the
> size of the codebase seems unnecessary. I think it does properly
> belong as part of the Axiom community
> 
> David
> 
> P.S. What does 'thomara' mean and have you done the appropriate name checks?


-- 
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: Axiom based XML Security Implementation

Posted by David Illsley <da...@gmail.com>.
Thanks for the information. I'm generally unconvinced by the argument
that having an optional 100KB axiom-xmlsecurity module counts as
'bloat'. To me it's better for users for it to be part of Axiom
because information about this additional functionality that Axiom
users may wish to use will be more obvious. From an Apache
perspective, I think having it part of Axiom would have a couple of
advantages...
1. Fewer dependency projects which need to be lined up for new
releases of e.f. Axis2/Rampart2
2. Giving it a separate name encourages people to think of it as
something separate and owned by a separate community which, given the
size of the codebase seems unnecessary. I think it does properly
belong as part of the Axiom community

David

P.S. What does 'thomara' mean and have you done the appropriate name checks?

Re: Axiom based XML Security Implementation

Posted by Saliya Ekanayake <es...@gmail.com>.
Hi David,

This was developed as part of our Final Year project in undergraduate
studies at the Dept. of Computer Science & Engineering, University of
Moratuwa, Sri Lanka. Regarding the concern about the place for this code, I
feel it should be a separate project. I am suggesting this because XML
Security may not be mandatory for everybody who are willing to use Axiom.
Thus, adding it inside Axiom will make it bit bloat. Apart from that, since
this can be developed further into a level as that of Apache XML Security
project it would be good if we maintain a separate project.

Your thoughts are welcome on this.

Thanks,
Saliya

On Tue, Feb 17, 2009 at 11:33 PM, David Illsley <da...@gmail.com>wrote:

> Great to have this code... I have a couple of thoughts...
>
> Firstly, where was this code developed? It looks like a bulk
> contribution to me, so I suspect it should really go through the IP
> clearance process [1]
>
> Secondly, should it really be a separate commons project? The commons
> already suffers from lots of small projects that have few committers
> and with poor visibility. I wonder if it would be better to make it
> part of Axiom and promote Axiom to be a full sub project. Thoughts?
>
> David
>
> [1] http://incubator.apache.org/ip-clearance/index.html
>



-- 
Saliya Ekanayake
http://www.esaliya.blogspot.com
http://www.esaliya.wordpress.com

Re: Axiom based XML Security Implementation

Posted by Sameera Jayasoma <sa...@gmail.com>.
On Tue, Feb 17, 2009 at 11:33 PM, David Illsley <da...@gmail.com>wrote:

> Great to have this code... I have a couple of thoughts...
>
> Firstly, where was this code developed? It looks like a bulk
> contribution to me, so I suspect it should really go through the IP
> clearance process [1]
>
> Secondly, should it really be a separate commons project? The commons
> already suffers from lots of small projects that have few committers
> and with poor visibility. I wonder if it would be better to make it
> part of Axiom and promote Axiom to be a full sub project. Thoughts?


I also believe that Thomara should not be a part of Axiom. It is an Axiom
based XML Security implementation. Now that there are several proven
projects based on Axiom, I think Axiom can be promoted as a full sub
project.

Thanks
Sameera

>
>
> David
>
> [1] http://incubator.apache.org/ip-clearance/index.html
>



-- 
Sameera Jayasoma
Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/

blog: http://tech.jayasoma.org

Re: Axiom based XML Security Implementation

Posted by David Illsley <da...@gmail.com>.
Great to have this code... I have a couple of thoughts...

Firstly, where was this code developed? It looks like a bulk
contribution to me, so I suspect it should really go through the IP
clearance process [1]

Secondly, should it really be a separate commons project? The commons
already suffers from lots of small projects that have few committers
and with poor visibility. I wonder if it would be better to make it
part of Axiom and promote Axiom to be a full sub project. Thoughts?

David

[1] http://incubator.apache.org/ip-clearance/index.html

Re: Axiom based XML Security Implementation

Posted by Ruchith Fernando <ru...@gmail.com>.
Great to see this code coming in! :-)

On Tue, Feb 17, 2009 at 6:50 AM, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> As we all know there are some performance issues with Rampart as the
> security module for Axis2. The main cause of this issue is the usage of DOM
> in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> http://santuario.apache.org/index.html) on which Rampart is written.
> Therefore as a research project, four of us (Sameera Jayasoma, Saliya
> Ekanayake, Kalani Ruwanpathirana and myself) have implemented a WS-Security
> implementation totally on Axiom. It consists of two layers and the bottom
> layer handles the xml security stuff. So we thought of adding this Axiom
> based xml securiy implementation as a new ws-commons project.
>
> Saliya has already created a jira at
> https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code is
> attached to the jira. This code is already tested and provides the same
> functionality as xmlsec with better performance.
>
> We have decided to use the name "thomara" for this and I'm planning to
> commit this code at
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara.
> Comments please?..

+1

Thanks,
Ruchith

>
> Thanks,
> Isuru
>



-- 
http://ruchith.org

Re: Axiom based XML Security Implementation

Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Benson, the name's just a name .. there's no translation of names!

I'm +1 for keeping the name as the authors want, assuming it has no legal 
issues.

Sanjiva.

Benson Margulies wrote:
> Can someone explain the relationship of the code to Axiom? CXF could
> benefit from a fast, standard-compliant, non-DOM platform here. I'm
> wondering if there is any refactoring possibility that could lead to
> sharing between the Axis2 stack and CXF here. Also, is the name
> translatable to English?
> 
> On Tue, Feb 17, 2009 at 7:15 AM, Ruwan Linton <ru...@gmail.com> wrote:
>> +1 for this, it will be a good addition.
>>
>> Thanks,
>> Ruwan
>>
>> On Tue, Feb 17, 2009 at 5:40 PM, Afkham Azeez <af...@gmail.com> wrote:
>>
>>> +1 for adding this project to the commons project. I don't like  the
>>> name though.
>>>
>>> Thanks
>>> Azeez
>>>
>>> On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com>
>>> wrote:
>>>> Hi all,
>>>>
>>>> As we all know there are some performance issues with Rampart as the
>>>> security module for Axis2. The main cause of this issue is the usage of
>>> DOM
>>>> in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
>>>> http://santuario.apache.org/index.html) on which Rampart is written.
>>>> Therefore as a research project, four of us (Sameera Jayasoma, Saliya
>>>> Ekanayake, Kalani Ruwanpathirana and myself) have implemented a
>>> WS-Security
>>>> implementation totally on Axiom. It consists of two layers and the bottom
>>>> layer handles the xml security stuff. So we thought of adding this Axiom
>>>> based xml securiy implementation as a new ws-commons project.
>>>>
>>>> Saliya has already created a jira at
>>>> https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code
>>> is
>>>> attached to the jira. This code is already tested and provides the same
>>>> functionality as xmlsec with better performance.
>>>>
>>>> We have decided to use the name "thomara" for this and I'm planning to
>>>> commit this code at
>>>>
>>> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
>>> .
>>>> Comments please?..
>>>>
>>>> Thanks,
>>>> Isuru
>>>>
>>>
>>>
>>> --
>>> Thanks
>>> Afkham Azeez
>>>
>>> Blog: http://afkham.org
>>> Developer Portal: http://www.wso2.org
>>> WSAS Blog: http://wso2wsas.blogspot.com
>>> Company: http://wso2.com
>>> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
>>>
>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>>


-- 
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/

Blog: http://sanjiva.weerawarana.org/

Re: Axiom based XML Security Implementation

Posted by Saliya Ekanayake <es...@gmail.com>.
Hi Benson,

The XML Security implementation uses Axiom in manipulating XML. Additionally
it uses Axiom's XML Canonicalization module. Thus, it implements XML
Signature and XML Encryption specifications. The API provided by the
particular implementation provides a similar API as that of Apache of XML
Security project (http://santuario.apache.org/Java/index.html).

Please find an initial performance evaluation of the overall Axiom based WS
Security implementation (code named "Rampart2") Vs Rampart at
http://wssecforaxis2.blogspot.com/2008/10/axis2-performance-with-ws-security.html

Thanks,
Saliya

On Tue, Feb 17, 2009 at 7:53 PM, Isuru Suriarachchi <is...@gmail.com>wrote:

> On Tue, Feb 17, 2009 at 6:25 PM, Benson Margulies <bimargulies@gmail.com
> >wrote:
>
> > Can someone explain the relationship of the code to Axiom?
>
>
> This xml security implementation (thomara) uses Axiom as the object model
> which keeps the xml infoset. This is to overcome the issues like memory
> wastage which exists in DOM based implementations. And also this removes
> the
> Axiom to DOM conversion which is done in Rampart at the moment.
>
>
> > CXF could
> > benefit from a fast, standard-compliant, non-DOM platform here. I'm
> > wondering if there is any refactoring possibility that could lead to
> > sharing between the Axis2 stack and CXF here.
>
>
> Rampart and Rampart2 differs only on the Axiom usage and architectural
> improvements in the WS-Security implementation of Rampart2. Other than
> that,
> the APIs of Rampart and Rampart2 are almost the same. Therefore I think CXF
> can't use Rampart2 directly.
>
> Thanks,
> Isuru
>
>
> > Also, is the name
> > translatable to English?
> >
> > On Tue, Feb 17, 2009 at 7:15 AM, Ruwan Linton <ru...@gmail.com>
> > wrote:
> > > +1 for this, it will be a good addition.
> > >
> > > Thanks,
> > > Ruwan
> > >
> > > On Tue, Feb 17, 2009 at 5:40 PM, Afkham Azeez <af...@gmail.com>
> wrote:
> > >
> > >> +1 for adding this project to the commons project. I don't like  the
> > >> name though.
> > >>
> > >> Thanks
> > >> Azeez
> > >>
> > >> On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <
> isurues@gmail.com>
> > >> wrote:
> > >> > Hi all,
> > >> >
> > >> > As we all know there are some performance issues with Rampart as the
> > >> > security module for Axis2. The main cause of this issue is the usage
> > of
> > >> DOM
> > >> > in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> > >> > http://santuario.apache.org/index.html) on which Rampart is
> written.
> > >> > Therefore as a research project, four of us (Sameera Jayasoma,
> Saliya
> > >> > Ekanayake, Kalani Ruwanpathirana and myself) have implemented a
> > >> WS-Security
> > >> > implementation totally on Axiom. It consists of two layers and the
> > bottom
> > >> > layer handles the xml security stuff. So we thought of adding this
> > Axiom
> > >> > based xml securiy implementation as a new ws-commons project.
> > >> >
> > >> > Saliya has already created a jira at
> > >> > https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source
> > code
> > >> is
> > >> > attached to the jira. This code is already tested and provides the
> > same
> > >> > functionality as xmlsec with better performance.
> > >> >
> > >> > We have decided to use the name "thomara" for this and I'm planning
> to
> > >> > commit this code at
> > >> >
> > >>
> >
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
> > >> .
> > >> > Comments please?..
> > >> >
> > >> > Thanks,
> > >> > Isuru
> > >> >
> > >>
> > >>
> > >>
> > >> --
> > >> Thanks
> > >> Afkham Azeez
> > >>
> > >> Blog: http://afkham.org
> > >> Developer Portal: http://www.wso2.org
> > >> WSAS Blog: http://wso2wsas.blogspot.com
> > >> Company: http://wso2.com
> > >> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
> > >>
> > >
> > >
> > >
> > > --
> > > Ruwan Linton
> > > http://wso2.org - "Oxygenating the Web Services Platform"
> > > http://ruwansblog.blogspot.com/
> > >
> >
>
>
>
> --
> Software Engineer,
> WSO2 Inc. http://wso2.org/
> Blog : http://isurues.wordpress.com/
>



-- 
Saliya Ekanayake
http://www.esaliya.blogspot.com
http://www.esaliya.wordpress.com

Re: Axiom based XML Security Implementation

Posted by Isuru Suriarachchi <is...@gmail.com>.
On Tue, Feb 17, 2009 at 6:25 PM, Benson Margulies <bi...@gmail.com>wrote:

> Can someone explain the relationship of the code to Axiom?


This xml security implementation (thomara) uses Axiom as the object model
which keeps the xml infoset. This is to overcome the issues like memory
wastage which exists in DOM based implementations. And also this removes the
Axiom to DOM conversion which is done in Rampart at the moment.


> CXF could
> benefit from a fast, standard-compliant, non-DOM platform here. I'm
> wondering if there is any refactoring possibility that could lead to
> sharing between the Axis2 stack and CXF here.


Rampart and Rampart2 differs only on the Axiom usage and architectural
improvements in the WS-Security implementation of Rampart2. Other than that,
the APIs of Rampart and Rampart2 are almost the same. Therefore I think CXF
can't use Rampart2 directly.

Thanks,
Isuru


> Also, is the name
> translatable to English?
>
> On Tue, Feb 17, 2009 at 7:15 AM, Ruwan Linton <ru...@gmail.com>
> wrote:
> > +1 for this, it will be a good addition.
> >
> > Thanks,
> > Ruwan
> >
> > On Tue, Feb 17, 2009 at 5:40 PM, Afkham Azeez <af...@gmail.com> wrote:
> >
> >> +1 for adding this project to the commons project. I don't like  the
> >> name though.
> >>
> >> Thanks
> >> Azeez
> >>
> >> On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com>
> >> wrote:
> >> > Hi all,
> >> >
> >> > As we all know there are some performance issues with Rampart as the
> >> > security module for Axis2. The main cause of this issue is the usage
> of
> >> DOM
> >> > in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> >> > http://santuario.apache.org/index.html) on which Rampart is written.
> >> > Therefore as a research project, four of us (Sameera Jayasoma, Saliya
> >> > Ekanayake, Kalani Ruwanpathirana and myself) have implemented a
> >> WS-Security
> >> > implementation totally on Axiom. It consists of two layers and the
> bottom
> >> > layer handles the xml security stuff. So we thought of adding this
> Axiom
> >> > based xml securiy implementation as a new ws-commons project.
> >> >
> >> > Saliya has already created a jira at
> >> > https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source
> code
> >> is
> >> > attached to the jira. This code is already tested and provides the
> same
> >> > functionality as xmlsec with better performance.
> >> >
> >> > We have decided to use the name "thomara" for this and I'm planning to
> >> > commit this code at
> >> >
> >>
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
> >> .
> >> > Comments please?..
> >> >
> >> > Thanks,
> >> > Isuru
> >> >
> >>
> >>
> >>
> >> --
> >> Thanks
> >> Afkham Azeez
> >>
> >> Blog: http://afkham.org
> >> Developer Portal: http://www.wso2.org
> >> WSAS Blog: http://wso2wsas.blogspot.com
> >> Company: http://wso2.com
> >> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
> >>
> >
> >
> >
> > --
> > Ruwan Linton
> > http://wso2.org - "Oxygenating the Web Services Platform"
> > http://ruwansblog.blogspot.com/
> >
>



-- 
Software Engineer,
WSO2 Inc. http://wso2.org/
Blog : http://isurues.wordpress.com/

Re: Axiom based XML Security Implementation

Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
IFAIK, they have written WS Security implementation on top of this which is
code named Rampart2 at the moment which uses "Thomara" the xml security
implementation. I am sure CXF can use "Thomara" as it is to do the xml
security stuff. But CXF won't be able to use Rampart2, so will have to write
something to bridge the gap. Other option is to get WSS4J to use this
implementation, so CXF will benifit from this.

And about the name, I think we can start a separate thread here, propose and
vote on the names and resolve it the apache way.

thanks,
nandana

On Tue, Feb 17, 2009 at 6:25 PM, Benson Margulies <bi...@gmail.com>wrote:

> Can someone explain the relationship of the code to Axiom? CXF could
> benefit from a fast, standard-compliant, non-DOM platform here. I'm
> wondering if there is any refactoring possibility that could lead to
> sharing between the Axis2 stack and CXF here. Also, is the name
> translatable to English?
>
> On Tue, Feb 17, 2009 at 7:15 AM, Ruwan Linton <ru...@gmail.com>
> wrote:
> > +1 for this, it will be a good addition.
> >
> > Thanks,
> > Ruwan
> >
> > On Tue, Feb 17, 2009 at 5:40 PM, Afkham Azeez <af...@gmail.com> wrote:
> >
> >> +1 for adding this project to the commons project. I don't like  the
> >> name though.
> >>
> >> Thanks
> >> Azeez
> >>
> >> On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com>
> >> wrote:
> >> > Hi all,
> >> >
> >> > As we all know there are some performance issues with Rampart as the
> >> > security module for Axis2. The main cause of this issue is the usage
> of
> >> DOM
> >> > in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> >> > http://santuario.apache.org/index.html) on which Rampart is written.
> >> > Therefore as a research project, four of us (Sameera Jayasoma, Saliya
> >> > Ekanayake, Kalani Ruwanpathirana and myself) have implemented a
> >> WS-Security
> >> > implementation totally on Axiom. It consists of two layers and the
> bottom
> >> > layer handles the xml security stuff. So we thought of adding this
> Axiom
> >> > based xml securiy implementation as a new ws-commons project.
> >> >
> >> > Saliya has already created a jira at
> >> > https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source
> code
> >> is
> >> > attached to the jira. This code is already tested and provides the
> same
> >> > functionality as xmlsec with better performance.
> >> >
> >> > We have decided to use the name "thomara" for this and I'm planning to
> >> > commit this code at
> >> >
> >>
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
> >> .
> >> > Comments please?..
> >> >
> >> > Thanks,
> >> > Isuru
> >> >
> >>
> >>
> >>
> >> --
> >> Thanks
> >> Afkham Azeez
> >>
> >> Blog: http://afkham.org
> >> Developer Portal: http://www.wso2.org
> >> WSAS Blog: http://wso2wsas.blogspot.com
> >> Company: http://wso2.com
> >> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
> >>
> >
> >
> >
> > --
> > Ruwan Linton
> > http://wso2.org - "Oxygenating the Web Services Platform"
> > http://ruwansblog.blogspot.com/
> >
>



-- 
Nandana Mihindukulasooriya
WSO2 inc.

http://nandana83.blogspot.com/
http://www.wso2.org

Re: Axiom based XML Security Implementation

Posted by Benson Margulies <bi...@gmail.com>.
Can someone explain the relationship of the code to Axiom? CXF could
benefit from a fast, standard-compliant, non-DOM platform here. I'm
wondering if there is any refactoring possibility that could lead to
sharing between the Axis2 stack and CXF here. Also, is the name
translatable to English?

On Tue, Feb 17, 2009 at 7:15 AM, Ruwan Linton <ru...@gmail.com> wrote:
> +1 for this, it will be a good addition.
>
> Thanks,
> Ruwan
>
> On Tue, Feb 17, 2009 at 5:40 PM, Afkham Azeez <af...@gmail.com> wrote:
>
>> +1 for adding this project to the commons project. I don't like  the
>> name though.
>>
>> Thanks
>> Azeez
>>
>> On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com>
>> wrote:
>> > Hi all,
>> >
>> > As we all know there are some performance issues with Rampart as the
>> > security module for Axis2. The main cause of this issue is the usage of
>> DOM
>> > in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
>> > http://santuario.apache.org/index.html) on which Rampart is written.
>> > Therefore as a research project, four of us (Sameera Jayasoma, Saliya
>> > Ekanayake, Kalani Ruwanpathirana and myself) have implemented a
>> WS-Security
>> > implementation totally on Axiom. It consists of two layers and the bottom
>> > layer handles the xml security stuff. So we thought of adding this Axiom
>> > based xml securiy implementation as a new ws-commons project.
>> >
>> > Saliya has already created a jira at
>> > https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code
>> is
>> > attached to the jira. This code is already tested and provides the same
>> > functionality as xmlsec with better performance.
>> >
>> > We have decided to use the name "thomara" for this and I'm planning to
>> > commit this code at
>> >
>> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
>> .
>> > Comments please?..
>> >
>> > Thanks,
>> > Isuru
>> >
>>
>>
>>
>> --
>> Thanks
>> Afkham Azeez
>>
>> Blog: http://afkham.org
>> Developer Portal: http://www.wso2.org
>> WSAS Blog: http://wso2wsas.blogspot.com
>> Company: http://wso2.com
>> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
>>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
>

Re: Axiom based XML Security Implementation

Posted by Ruwan Linton <ru...@gmail.com>.
+1 for this, it will be a good addition.

Thanks,
Ruwan

On Tue, Feb 17, 2009 at 5:40 PM, Afkham Azeez <af...@gmail.com> wrote:

> +1 for adding this project to the commons project. I don't like  the
> name though.
>
> Thanks
> Azeez
>
> On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com>
> wrote:
> > Hi all,
> >
> > As we all know there are some performance issues with Rampart as the
> > security module for Axis2. The main cause of this issue is the usage of
> DOM
> > in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> > http://santuario.apache.org/index.html) on which Rampart is written.
> > Therefore as a research project, four of us (Sameera Jayasoma, Saliya
> > Ekanayake, Kalani Ruwanpathirana and myself) have implemented a
> WS-Security
> > implementation totally on Axiom. It consists of two layers and the bottom
> > layer handles the xml security stuff. So we thought of adding this Axiom
> > based xml securiy implementation as a new ws-commons project.
> >
> > Saliya has already created a jira at
> > https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code
> is
> > attached to the jira. This code is already tested and provides the same
> > functionality as xmlsec with better performance.
> >
> > We have decided to use the name "thomara" for this and I'm planning to
> > commit this code at
> >
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
> .
> > Comments please?..
> >
> > Thanks,
> > Isuru
> >
>
>
>
> --
> Thanks
> Afkham Azeez
>
> Blog: http://afkham.org
> Developer Portal: http://www.wso2.org
> WSAS Blog: http://wso2wsas.blogspot.com
> Company: http://wso2.com
> GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760
>



-- 
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/

Re: Axiom based XML Security Implementation

Posted by Afkham Azeez <af...@gmail.com>.
+1 for adding this project to the commons project. I don't like  the
name though.

Thanks
Azeez

On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com> wrote:
> Hi all,
>
> As we all know there are some performance issues with Rampart as the
> security module for Axis2. The main cause of this issue is the usage of DOM
> in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> http://santuario.apache.org/index.html) on which Rampart is written.
> Therefore as a research project, four of us (Sameera Jayasoma, Saliya
> Ekanayake, Kalani Ruwanpathirana and myself) have implemented a WS-Security
> implementation totally on Axiom. It consists of two layers and the bottom
> layer handles the xml security stuff. So we thought of adding this Axiom
> based xml securiy implementation as a new ws-commons project.
>
> Saliya has already created a jira at
> https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code is
> attached to the jira. This code is already tested and provides the same
> functionality as xmlsec with better performance.
>
> We have decided to use the name "thomara" for this and I'm planning to
> commit this code at
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara.
> Comments please?..
>
> Thanks,
> Isuru
>



-- 
Thanks
Afkham Azeez

Blog: http://afkham.org
Developer Portal: http://www.wso2.org
WSAS Blog: http://wso2wsas.blogspot.com
Company: http://wso2.com
GPG Fingerprint: 643F C2AF EB78 F886 40C9  B2A2 4AE2 C887 665E 0760

Re: Axiom based XML Security Implementation

Posted by Nandana Mihindukulasooriya <na...@gmail.com>.
+1, Would be a great addition to the Apache commons project.

thanks,
nandana

On Tue, Feb 17, 2009 at 5:20 PM, Isuru Suriarachchi <is...@gmail.com>wrote:

> Hi all,
>
> As we all know there are some performance issues with Rampart as the
> security module for Axis2. The main cause of this issue is the usage of DOM
> in wss4j (http://ws.apache.org/wss4j/) and xmlsec (
> http://santuario.apache.org/index.html) on which Rampart is written.
> Therefore as a research project, four of us (Sameera Jayasoma, Saliya
> Ekanayake, Kalani Ruwanpathirana and myself) have implemented a WS-Security
> implementation totally on Axiom. It consists of two layers and the bottom
> layer handles the xml security stuff. So we thought of adding this Axiom
> based xml securiy implementation as a new ws-commons project.
>
> Saliya has already created a jira at
> https://issues.apache.org/jira/browse/WSCOMMONS-441 and the source code is
> attached to the jira. This code is already tested and provides the same
> functionality as xmlsec with better performance.
>
> We have decided to use the name "thomara" for this and I'm planning to
> commit this code at
> https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/thomara
> .
> Comments please?..
>
> Thanks,
> Isuru
>