You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by Ajith Ranabahu <aj...@gmail.com> on 2006/09/01 00:42:26 UTC
Re: WSS4J 2.0(?)
Hi,
I'm also +1 on this move - it makes things modular and easy to handle.
BTW I don't think you need to move the integration tests - they are
*Axis2* integration tests and they should not go to any other project!
Of course the rampart module will be external after the change but
that does not mean that the integration tests have to be too :)
I would also like to draw your attention to the structure of the
projects as well. If you look at the current project structure almost
all the projects that are under the ws project space are mostly
independent of each other [1]. For example WSS4J,Woden (which is
really incubated) and other tit bits in ws-commons. It is true that
there are projects that are explicitly focused on adding support to
other projects (like Kandula and Sandesha) but what I feel is that
since Savan and rampart are going to be very Axis2 specific, they
would not fit as immediate children of the ws project space. To me it
makes good sense to have a sub project called Axis2-modules (whatever
the name you guys prefer. I don't want it to be another naming war :))
and have savan and rampart under that - just like what we have in
ws-commons right now.
do I make any sense ?
Ajith
[1] http://ws.apache.org/#Project+List
On 8/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Another big +1 from me too.
>
> I was really worried about the increasing number of modules within Axis2
> project, but didn't take this up as people were busy with other
> important issues. I'd like to add two more things to Ruchith's proposal.
>
> 1. Move Savan also to a sub-project out of Axis2
>
> 2. Write some integration tests in Axis2 to compensate the valuable
> tests Ruchith had written to test the integrity of Axis2 client and
> server. Whenever you do some random changes in Axis2, security tests
> were failing as they were the only tests which tested the real
> integration. Since these tests also will be moved with Rahas and
> Rampart, we need to have some tests to compensate them
>
> 3. Need to have a gump like thingy setup to run all the tests in Axis2
> and related projects and to bug whoever breaks the total build.
>
> Any volunteers?
>
> -- Chinthaka
>
> Sanjiva Weerawarana wrote:
> > On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote:
> >> Basically how about pushing these up to be two new sub projects or the
> >> Apache Web services project :
> >>
> >> Ramaprt - WS-Security and WS-SecureConversation implementation
> >> Rahas - WS-Trust implementation
> >>
> >> This is similar to the way we have Sandesha (WS-RM impl), and they
> >> will have their own release cycles etc. ?
> >
> > Big +1 from me. I don't see any need to clutter up WSS4J with all this
> > stuff - let's keep WSS4J at the level it is and add separate projects to
> > cover the other functionality (which are Axis2 and Axiom coupled
> > anyway).
> >
> > Sanjiva.
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
>
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi,
On 9/1/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Unfortunately I do not agree with this.
>
> Are you saying integration tests of Rampart and Axis2 should live in
> Axis2? And you want to move Rampart out of Axis2?
> For me these are two contradictory statements.
>
> What if tomorrow, Sandesha, Kandula, Savan, etc., wants to have their
> tests within Axis2? Do you agree?
I see this boiling down to the following questions:
- Can we have a volunteer to develop a set of integration test cases
to test the features tested by rampart and rahas?
- If not AND if we still move the tests can we have a volunteer to
setup something like GUMP to send out an alert when there's a problem
in the dependant project due to a change in another?
If we cannot do any of the above, IMHO it is better to keep the tests in Axis2.
Thoughts?
Thanks,
Ruchith
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]
Posted by David Illsley <da...@gmail.com>.
What about neethi? With rahas, savan, security, sandesha, secpolicy
all being WS subprojects should neethi be also?
David
On 01/09/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Unfortunately I do not agree with this.
>
> Are you saying integration tests of Rampart and Axis2 should live in
> Axis2? And you want to move Rampart out of Axis2?
> For me these are two contradictory statements.
>
> What if tomorrow, Sandesha, Kandula, Savan, etc., wants to have their
> tests within Axis2? Do you agree?
>
> The ideal solution I'd like to see is Axis2 project which has
>
> 1. the core of Axis2 which includes:
>
> addressing
> adb
> adb-codegen
> codegen
> common
> integration (without rampart, rahas test cases)
> kernel
> samples
> webapp
> wsdl
> java2wsdl(we can move this out to commons)
>
> 2. The extension to Axis2 which are sub-projects of Axis2 which includes:
> jaxbri
> jaxws
> jibx
> saaj(having this in the core project is fine with me)
> spring
> tools
> xmlbeans
>
>
> 3. Different sub projects under WS project for:
> rahas
> savan
> security
> sandesha
> secpolicy
>
> 4. Promote Axiom and Xmlschema to separate TLPs.
>
> -- Chinthaka
>
>
>
>
> Ajith Ranabahu wrote:
> > Hi,
> > Nope I'm not missing anything :) I'm saying keep the integration tests
> > as it is (I'm talking about the security tests in the integration
> > module) and they can run having rampart as an external dependancy.
> > That's it. You don't want to move them anywhere. If Axis2 code is not
> > compatible with the latest rampart build (which now comes as an
> > external dependancy), Axis2 build will fail!
> > In my mind Axis2 integration tests belong in Axis2 and not anywhere
> > else. We do have XMLBeans and Jibx tests that way.
> >
> > Ajith
> >
> > On 9/1/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> >> Ajith Ranabahu wrote:
> >> > Hi,
> >> > I'm also +1 on this move - it makes things modular and easy to handle.
> >> > BTW I don't think you need to move the integration tests - they are
> >> > *Axis2* integration tests and they should not go to any other project!
> >>
> >> No, you miss something here Ajith. They are not mere integration tests.
> >> They test how Rahas or Rampart or whatever works hand-in-hand. But that
> >> includes Axis2 integration tests as well.
> >> Thats the reason behind me mentioning that we need some test cases to
> >> test the integration to compensate the removal of Security integration
> >> tests. Read point #2 my earlier mail.
> >>
> >> -- Chinthaka
> >>
> >>
> >>
> >>
> >
> >
>
>
>
>
>
--
David Illsley - IBM Web Services Development
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi All,
On 9/1/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Unfortunately I do not agree with this.
>
> Are you saying integration tests of Rampart and Axis2 should live in
> Axis2? And you want to move Rampart out of Axis2?
> For me these are two contradictory statements.
>
> What if tomorrow, Sandesha, Kandula, Savan, etc., wants to have their
> tests within Axis2? Do you agree?
>
> The ideal solution I'd like to see is Axis2 project which has
>
> 1. the core of Axis2 which includes:
>
> addressing
> adb
> adb-codegen
> codegen
> common
> integration (without rampart, rahas test cases)
> kernel
> samples
> webapp
> wsdl
> java2wsdl(we can move this out to commons)
>
> 2. The extension to Axis2 which are sub-projects of Axis2 which includes:
> jaxbri
> jaxws
> jibx
> saaj(having this in the core project is fine with me)
> spring
> tools
> xmlbeans
The core components of axis2 (#1 above) and the axis2 sub projects (#2
above) will be modules within axis2 right?
>
>
> 3. Different sub projects under WS project for:
> rahas
> savan
> security
> sandesha
+1
> secpolicy
I believe secpoliicy can move into ws-commons since its used by both
Rahas and Rampart.
>
> 4. Promote Axiom and Xmlschema to separate TLPs.
+1
Thanks,
Ruchith
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]
Posted by Eran Chinthaka <ch...@opensource.lk>.
Unfortunately I do not agree with this.
Are you saying integration tests of Rampart and Axis2 should live in
Axis2? And you want to move Rampart out of Axis2?
For me these are two contradictory statements.
What if tomorrow, Sandesha, Kandula, Savan, etc., wants to have their
tests within Axis2? Do you agree?
The ideal solution I'd like to see is Axis2 project which has
1. the core of Axis2 which includes:
addressing
adb
adb-codegen
codegen
common
integration (without rampart, rahas test cases)
kernel
samples
webapp
wsdl
java2wsdl(we can move this out to commons)
2. The extension to Axis2 which are sub-projects of Axis2 which includes:
jaxbri
jaxws
jibx
saaj(having this in the core project is fine with me)
spring
tools
xmlbeans
3. Different sub projects under WS project for:
rahas
savan
security
sandesha
secpolicy
4. Promote Axiom and Xmlschema to separate TLPs.
-- Chinthaka
Ajith Ranabahu wrote:
> Hi,
> Nope I'm not missing anything :) I'm saying keep the integration tests
> as it is (I'm talking about the security tests in the integration
> module) and they can run having rampart as an external dependancy.
> That's it. You don't want to move them anywhere. If Axis2 code is not
> compatible with the latest rampart build (which now comes as an
> external dependancy), Axis2 build will fail!
> In my mind Axis2 integration tests belong in Axis2 and not anywhere
> else. We do have XMLBeans and Jibx tests that way.
>
> Ajith
>
> On 9/1/06, Eran Chinthaka <ch...@opensource.lk> wrote:
>> Ajith Ranabahu wrote:
>> > Hi,
>> > I'm also +1 on this move - it makes things modular and easy to handle.
>> > BTW I don't think you need to move the integration tests - they are
>> > *Axis2* integration tests and they should not go to any other project!
>>
>> No, you miss something here Ajith. They are not mere integration tests.
>> They test how Rahas or Rampart or whatever works hand-in-hand. But that
>> includes Axis2 integration tests as well.
>> Thats the reason behind me mentioning that we need some test cases to
>> test the integration to compensate the removal of Security integration
>> tests. Read point #2 my earlier mail.
>>
>> -- Chinthaka
>>
>>
>>
>>
>
>
Re: WSS4J 2.0(?)
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
Nope I'm not missing anything :) I'm saying keep the integration tests
as it is (I'm talking about the security tests in the integration
module) and they can run having rampart as an external dependancy.
That's it. You don't want to move them anywhere. If Axis2 code is not
compatible with the latest rampart build (which now comes as an
external dependancy), Axis2 build will fail!
In my mind Axis2 integration tests belong in Axis2 and not anywhere
else. We do have XMLBeans and Jibx tests that way.
Ajith
On 9/1/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> Ajith Ranabahu wrote:
> > Hi,
> > I'm also +1 on this move - it makes things modular and easy to handle.
> > BTW I don't think you need to move the integration tests - they are
> > *Axis2* integration tests and they should not go to any other project!
>
> No, you miss something here Ajith. They are not mere integration tests.
> They test how Rahas or Rampart or whatever works hand-in-hand. But that
> includes Axis2 integration tests as well.
> Thats the reason behind me mentioning that we need some test cases to
> test the integration to compensate the removal of Security integration
> tests. Read point #2 my earlier mail.
>
> -- Chinthaka
>
>
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: WSS4J 2.0(?)
Posted by Eran Chinthaka <ch...@opensource.lk>.
Ajith Ranabahu wrote:
> Hi,
> I'm also +1 on this move - it makes things modular and easy to handle.
> BTW I don't think you need to move the integration tests - they are
> *Axis2* integration tests and they should not go to any other project!
No, you miss something here Ajith. They are not mere integration tests.
They test how Rahas or Rampart or whatever works hand-in-hand. But that
includes Axis2 integration tests as well.
Thats the reason behind me mentioning that we need some test cases to
test the integration to compensate the removal of Security integration
tests. Read point #2 my earlier mail.
-- Chinthaka
Re: WSS4J 2.0(?)
Posted by Eran Chinthaka <ch...@opensource.lk>.
Ruchith Fernando wrote:
> Hi,
>
> In the case of Axiom I think we can now consider it to be a very much
> general XML object model, and I believe it has many other users other
> than Axis2 and Axis2 related projects ... and it sure can be moved out
> of ws-commons (may be as a Apache TLP ??) and it probably will get
> more visibility and more ppl will use it.
Definite +1 for this. I know Tuscany and Abdera guys are using Axiom a
lot. Especially Abdera has nothing to do with Web services.
-- Chinthaka
Re: Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Oops, I did not mean to get them under WS*, we can keep them outside WS*
-Jaliya
On 9/1/06, Eran Chinthaka <ch...@opensource.lk> wrote:
>
> Jaliya Ekanayake wrote:
> > Hi All,
> >
> > Few thoughts from me.
> >
> > We cannot expect people to use QoS projects like Kandula and Sandesha
> > without axis1 or axis2 and also we can expect axiom and WSS4J to be used
> > more independently. In addition they all come under WS* projects. So I
> > would like to suggest this.
> >
>
> Jaliya did u mean Axiom also should come under WS*? If yes, I do not
> agree with you. I'd rather lean towards Ruchith's and Ajith's suggestion.
> Axiom, XmlSchema can be projects useful even outside WS*.
> If you mean the same thing, apologies in advance :). Just making sure we
> all are in the same camp.
>
> -- Chinthaka
>
>
>
>
Refactoring WS Projects [ Was : Re: WSS4J 2.0(?)]
Posted by Eran Chinthaka <ch...@opensource.lk>.
Jaliya Ekanayake wrote:
> Hi All,
>
> Few thoughts from me.
>
> We cannot expect people to use QoS projects like Kandula and Sandesha
> without axis1 or axis2 and also we can expect axiom and WSS4J to be used
> more independently. In addition they all come under WS* projects. So I
> would like to suggest this.
>
Jaliya did u mean Axiom also should come under WS*? If yes, I do not
agree with you. I'd rather lean towards Ruchith's and Ajith's suggestion.
Axiom, XmlSchema can be projects useful even outside WS*.
If you mean the same thing, apologies in advance :). Just making sure we
all are in the same camp.
-- Chinthaka
Re: WSS4J 2.0(?)
Posted by Jaliya Ekanayake <jn...@gmail.com>.
Hi All,
Few thoughts from me.
We cannot expect people to use QoS projects like Kandula and Sandesha
without axis1 or axis2 and also we can expect axiom and WSS4J to be used
more independently. In addition they all come under WS* projects. So I would
like to suggest this.
Let's make all these modules separate sub projects may be under WS* and then
have a clear definition of their tasks and compatibilities so that the sub
projects can have an SNAPSHOT of axis2 or axis1 and have its own development
cycles. (Similar to what we have for Sandesha and Kandula).
As Chinthaka mentioned we need those integration tests to be in axis2 and
also the sub projects should have a set of test cases to check their
compatibility with the latest axis2 version that they support.
In addition we need to have some links in the respective web pages for the
users to know what modules(sub projects) they should use to get the required
QoSs.
Thanks,
-Jaliya
----- Original Message -----
From: "Ruchith Fernando" <ru...@gmail.com>
To: <ax...@ws.apache.org>
Sent: Friday, September 01, 2006 4:56 AM
Subject: Re: WSS4J 2.0(?)
> Hi,
>
> In the case of Axiom I think we can now consider it to be a very much
> general XML object model, and I believe it has many other users other
> than Axis2 and Axis2 related projects ... and it sure can be moved out
> of ws-commons (may be as a Apache TLP ??) and it probably will get
> more visibility and more ppl will use it.
>
> As I mentioned earlier ... moved away from grouping WS-* impls when
> we flattened WS-FX ... If we group these projects again then ... are
> you suggesting we recreate something like WS-FX? In that case for
> example rampart/c will be a sub project of rampart project which is a
> sub project of the new ws-fx project which is a sub project of the
> Apache WS project. Sounds too deep to me :-(.
>
> Thanks,
> Ruchith
>
> On 9/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
>> Hi,
>> Ok, the fact that they are the home for their C counterparts is valid
>> to some extent to make it to the top level ( I mean as direct children
>> of WS project - subsequent uses of top level would mean the same
>> stated otherwise). But why did we place XMLSchema, Axiom, neethi,
>> tcpmon and such independent pieces of software inside ws-commons
>> then ? If we are promoting rampart, rahas and savan as ellegible to be
>> in the top level, Axiom, Neethi and XMLSchema deserve to come out of
>> their hiding as well :)
>> Simply what I'm trying to point out is this. Rampart, Rahas ans Savan
>> are very tightly bound to Axis2 and no one is able to use them as
>> 'standalone' pieces (As opposed to something like WSS4J which is not
>> bound to any such framework). It would be better to reflect this
>> obvious fact in the project structure as well.
>>
>> Ajith
>>
>> On 8/31/06, Ruchith Fernando <ru...@gmail.com> wrote:
>> > Ajith,
>> >
>> > If we implement this, it is going to be exactly similar to the WS-FX
>> > project ... which we got rid of, some time back !
>> >
>> > It is much more clearer to have the different WS-* implementations at
>> > direct children of the WS project.
>> >
>> > Also its important to note that these sub-projects (Rampart, Rahas,
>> > Sandesha, Kandula etc) will also provide a home for their
>> > implementations in other languages as well , such as C.
>> >
>> > Thanks,
>> > Ruchith
>> >
>> > On 9/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
>> > > Hi,
>> > > I'm also +1 on this move - it makes things modular and easy to
>> > > handle.
>> > > BTW I don't think you need to move the integration tests - they are
>> > > *Axis2* integration tests and they should not go to any other
>> > > project!
>> > > Of course the rampart module will be external after the change but
>> > > that does not mean that the integration tests have to be too :)
>> > > I would also like to draw your attention to the structure of the
>> > > projects as well. If you look at the current project structure almost
>> > > all the projects that are under the ws project space are mostly
>> > > independent of each other [1]. For example WSS4J,Woden (which is
>> > > really incubated) and other tit bits in ws-commons. It is true that
>> > > there are projects that are explicitly focused on adding support to
>> > > other projects (like Kandula and Sandesha) but what I feel is that
>> > > since Savan and rampart are going to be very Axis2 specific, they
>> > > would not fit as immediate children of the ws project space. To me it
>> > > makes good sense to have a sub project called Axis2-modules (whatever
>> > > the name you guys prefer. I don't want it to be another naming war
>> > > :))
>> > > and have savan and rampart under that - just like what we have in
>> > > ws-commons right now.
>> > >
>> > > do I make any sense ?
>> > >
>> > > Ajith
>> > >
>> > > [1] http://ws.apache.org/#Project+List
>> > >
>> > > On 8/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
>> > > > Another big +1 from me too.
>> > > >
>> > > > I was really worried about the increasing number of modules within
>> > > > Axis2
>> > > > project, but didn't take this up as people were busy with other
>> > > > important issues. I'd like to add two more things to Ruchith's
>> > > > proposal.
>> > > >
>> > > > 1. Move Savan also to a sub-project out of Axis2
>> > > >
>> > > > 2. Write some integration tests in Axis2 to compensate the valuable
>> > > > tests Ruchith had written to test the integrity of Axis2 client and
>> > > > server. Whenever you do some random changes in Axis2, security
>> > > > tests
>> > > > were failing as they were the only tests which tested the real
>> > > > integration. Since these tests also will be moved with Rahas and
>> > > > Rampart, we need to have some tests to compensate them
>> > > >
>> > > > 3. Need to have a gump like thingy setup to run all the tests in
>> > > > Axis2
>> > > > and related projects and to bug whoever breaks the total build.
>> > > >
>> > > > Any volunteers?
>> > > >
>> > > > -- Chinthaka
>> > > >
>> > > > Sanjiva Weerawarana wrote:
>> > > > > On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote:
>> > > > >> Basically how about pushing these up to be two new sub projects
>> > > > >> or the
>> > > > >> Apache Web services project :
>> > > > >>
>> > > > >> Ramaprt - WS-Security and WS-SecureConversation implementation
>> > > > >> Rahas - WS-Trust implementation
>> > > > >>
>> > > > >> This is similar to the way we have Sandesha (WS-RM impl), and
>> > > > >> they
>> > > > >> will have their own release cycles etc. ?
>> > > > >
>> > > > > Big +1 from me. I don't see any need to clutter up WSS4J with all
>> > > > > this
>> > > > > stuff - let's keep WSS4J at the level it is and add separate
>> > > > > projects to
>> > > > > cover the other functionality (which are Axis2 and Axiom coupled
>> > > > > anyway).
>> > > > >
>> > > > > Sanjiva.
>> > > > >
>> > > > >
>> > > > > ---------------------------------------------------------------------
>> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > > >
>> > >
>> > >
>> > > --
>> > > Ajith Ranabahu
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > >
>> > >
>> >
>> >
>> > --
>> > www.ruchith.org
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> >
>> >
>>
>>
>> --
>> Ajith Ranabahu
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
> --
> www.ruchith.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: WSS4J 2.0(?)
Posted by Ruchith Fernando <ru...@gmail.com>.
Hi,
In the case of Axiom I think we can now consider it to be a very much
general XML object model, and I believe it has many other users other
than Axis2 and Axis2 related projects ... and it sure can be moved out
of ws-commons (may be as a Apache TLP ??) and it probably will get
more visibility and more ppl will use it.
As I mentioned earlier ... moved away from grouping WS-* impls when
we flattened WS-FX ... If we group these projects again then ... are
you suggesting we recreate something like WS-FX? In that case for
example rampart/c will be a sub project of rampart project which is a
sub project of the new ws-fx project which is a sub project of the
Apache WS project. Sounds too deep to me :-(.
Thanks,
Ruchith
On 9/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> Hi,
> Ok, the fact that they are the home for their C counterparts is valid
> to some extent to make it to the top level ( I mean as direct children
> of WS project - subsequent uses of top level would mean the same
> stated otherwise). But why did we place XMLSchema, Axiom, neethi,
> tcpmon and such independent pieces of software inside ws-commons
> then ? If we are promoting rampart, rahas and savan as ellegible to be
> in the top level, Axiom, Neethi and XMLSchema deserve to come out of
> their hiding as well :)
> Simply what I'm trying to point out is this. Rampart, Rahas ans Savan
> are very tightly bound to Axis2 and no one is able to use them as
> 'standalone' pieces (As opposed to something like WSS4J which is not
> bound to any such framework). It would be better to reflect this
> obvious fact in the project structure as well.
>
> Ajith
>
> On 8/31/06, Ruchith Fernando <ru...@gmail.com> wrote:
> > Ajith,
> >
> > If we implement this, it is going to be exactly similar to the WS-FX
> > project ... which we got rid of, some time back !
> >
> > It is much more clearer to have the different WS-* implementations at
> > direct children of the WS project.
> >
> > Also its important to note that these sub-projects (Rampart, Rahas,
> > Sandesha, Kandula etc) will also provide a home for their
> > implementations in other languages as well , such as C.
> >
> > Thanks,
> > Ruchith
> >
> > On 9/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> > > Hi,
> > > I'm also +1 on this move - it makes things modular and easy to handle.
> > > BTW I don't think you need to move the integration tests - they are
> > > *Axis2* integration tests and they should not go to any other project!
> > > Of course the rampart module will be external after the change but
> > > that does not mean that the integration tests have to be too :)
> > > I would also like to draw your attention to the structure of the
> > > projects as well. If you look at the current project structure almost
> > > all the projects that are under the ws project space are mostly
> > > independent of each other [1]. For example WSS4J,Woden (which is
> > > really incubated) and other tit bits in ws-commons. It is true that
> > > there are projects that are explicitly focused on adding support to
> > > other projects (like Kandula and Sandesha) but what I feel is that
> > > since Savan and rampart are going to be very Axis2 specific, they
> > > would not fit as immediate children of the ws project space. To me it
> > > makes good sense to have a sub project called Axis2-modules (whatever
> > > the name you guys prefer. I don't want it to be another naming war :))
> > > and have savan and rampart under that - just like what we have in
> > > ws-commons right now.
> > >
> > > do I make any sense ?
> > >
> > > Ajith
> > >
> > > [1] http://ws.apache.org/#Project+List
> > >
> > > On 8/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > > > Another big +1 from me too.
> > > >
> > > > I was really worried about the increasing number of modules within Axis2
> > > > project, but didn't take this up as people were busy with other
> > > > important issues. I'd like to add two more things to Ruchith's proposal.
> > > >
> > > > 1. Move Savan also to a sub-project out of Axis2
> > > >
> > > > 2. Write some integration tests in Axis2 to compensate the valuable
> > > > tests Ruchith had written to test the integrity of Axis2 client and
> > > > server. Whenever you do some random changes in Axis2, security tests
> > > > were failing as they were the only tests which tested the real
> > > > integration. Since these tests also will be moved with Rahas and
> > > > Rampart, we need to have some tests to compensate them
> > > >
> > > > 3. Need to have a gump like thingy setup to run all the tests in Axis2
> > > > and related projects and to bug whoever breaks the total build.
> > > >
> > > > Any volunteers?
> > > >
> > > > -- Chinthaka
> > > >
> > > > Sanjiva Weerawarana wrote:
> > > > > On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote:
> > > > >> Basically how about pushing these up to be two new sub projects or the
> > > > >> Apache Web services project :
> > > > >>
> > > > >> Ramaprt - WS-Security and WS-SecureConversation implementation
> > > > >> Rahas - WS-Trust implementation
> > > > >>
> > > > >> This is similar to the way we have Sandesha (WS-RM impl), and they
> > > > >> will have their own release cycles etc. ?
> > > > >
> > > > > Big +1 from me. I don't see any need to clutter up WSS4J with all this
> > > > > stuff - let's keep WSS4J at the level it is and add separate projects to
> > > > > cover the other functionality (which are Axis2 and Axiom coupled
> > > > > anyway).
> > > > >
> > > > > Sanjiva.
> > > > >
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > > >
> > > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > >
> > > --
> > > Ajith Ranabahu
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> > --
> > www.ruchith.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Ajith Ranabahu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
www.ruchith.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: WSS4J 2.0(?)
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
Ok, the fact that they are the home for their C counterparts is valid
to some extent to make it to the top level ( I mean as direct children
of WS project - subsequent uses of top level would mean the same
stated otherwise). But why did we place XMLSchema, Axiom, neethi,
tcpmon and such independent pieces of software inside ws-commons
then ? If we are promoting rampart, rahas and savan as ellegible to be
in the top level, Axiom, Neethi and XMLSchema deserve to come out of
their hiding as well :)
Simply what I'm trying to point out is this. Rampart, Rahas ans Savan
are very tightly bound to Axis2 and no one is able to use them as
'standalone' pieces (As opposed to something like WSS4J which is not
bound to any such framework). It would be better to reflect this
obvious fact in the project structure as well.
Ajith
On 8/31/06, Ruchith Fernando <ru...@gmail.com> wrote:
> Ajith,
>
> If we implement this, it is going to be exactly similar to the WS-FX
> project ... which we got rid of, some time back !
>
> It is much more clearer to have the different WS-* implementations at
> direct children of the WS project.
>
> Also its important to note that these sub-projects (Rampart, Rahas,
> Sandesha, Kandula etc) will also provide a home for their
> implementations in other languages as well , such as C.
>
> Thanks,
> Ruchith
>
> On 9/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> > Hi,
> > I'm also +1 on this move - it makes things modular and easy to handle.
> > BTW I don't think you need to move the integration tests - they are
> > *Axis2* integration tests and they should not go to any other project!
> > Of course the rampart module will be external after the change but
> > that does not mean that the integration tests have to be too :)
> > I would also like to draw your attention to the structure of the
> > projects as well. If you look at the current project structure almost
> > all the projects that are under the ws project space are mostly
> > independent of each other [1]. For example WSS4J,Woden (which is
> > really incubated) and other tit bits in ws-commons. It is true that
> > there are projects that are explicitly focused on adding support to
> > other projects (like Kandula and Sandesha) but what I feel is that
> > since Savan and rampart are going to be very Axis2 specific, they
> > would not fit as immediate children of the ws project space. To me it
> > makes good sense to have a sub project called Axis2-modules (whatever
> > the name you guys prefer. I don't want it to be another naming war :))
> > and have savan and rampart under that - just like what we have in
> > ws-commons right now.
> >
> > do I make any sense ?
> >
> > Ajith
> >
> > [1] http://ws.apache.org/#Project+List
> >
> > On 8/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > > Another big +1 from me too.
> > >
> > > I was really worried about the increasing number of modules within Axis2
> > > project, but didn't take this up as people were busy with other
> > > important issues. I'd like to add two more things to Ruchith's proposal.
> > >
> > > 1. Move Savan also to a sub-project out of Axis2
> > >
> > > 2. Write some integration tests in Axis2 to compensate the valuable
> > > tests Ruchith had written to test the integrity of Axis2 client and
> > > server. Whenever you do some random changes in Axis2, security tests
> > > were failing as they were the only tests which tested the real
> > > integration. Since these tests also will be moved with Rahas and
> > > Rampart, we need to have some tests to compensate them
> > >
> > > 3. Need to have a gump like thingy setup to run all the tests in Axis2
> > > and related projects and to bug whoever breaks the total build.
> > >
> > > Any volunteers?
> > >
> > > -- Chinthaka
> > >
> > > Sanjiva Weerawarana wrote:
> > > > On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote:
> > > >> Basically how about pushing these up to be two new sub projects or the
> > > >> Apache Web services project :
> > > >>
> > > >> Ramaprt - WS-Security and WS-SecureConversation implementation
> > > >> Rahas - WS-Trust implementation
> > > >>
> > > >> This is similar to the way we have Sandesha (WS-RM impl), and they
> > > >> will have their own release cycles etc. ?
> > > >
> > > > Big +1 from me. I don't see any need to clutter up WSS4J with all this
> > > > stuff - let's keep WSS4J at the level it is and add separate projects to
> > > > cover the other functionality (which are Axis2 and Axiom coupled
> > > > anyway).
> > > >
> > > > Sanjiva.
> > > >
> > > >
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Ajith Ranabahu
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> www.ruchith.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: WSS4J 2.0(?)
Posted by Ruchith Fernando <ru...@gmail.com>.
Ajith,
If we implement this, it is going to be exactly similar to the WS-FX
project ... which we got rid of, some time back !
It is much more clearer to have the different WS-* implementations at
direct children of the WS project.
Also its important to note that these sub-projects (Rampart, Rahas,
Sandesha, Kandula etc) will also provide a home for their
implementations in other languages as well , such as C.
Thanks,
Ruchith
On 9/1/06, Ajith Ranabahu <aj...@gmail.com> wrote:
> Hi,
> I'm also +1 on this move - it makes things modular and easy to handle.
> BTW I don't think you need to move the integration tests - they are
> *Axis2* integration tests and they should not go to any other project!
> Of course the rampart module will be external after the change but
> that does not mean that the integration tests have to be too :)
> I would also like to draw your attention to the structure of the
> projects as well. If you look at the current project structure almost
> all the projects that are under the ws project space are mostly
> independent of each other [1]. For example WSS4J,Woden (which is
> really incubated) and other tit bits in ws-commons. It is true that
> there are projects that are explicitly focused on adding support to
> other projects (like Kandula and Sandesha) but what I feel is that
> since Savan and rampart are going to be very Axis2 specific, they
> would not fit as immediate children of the ws project space. To me it
> makes good sense to have a sub project called Axis2-modules (whatever
> the name you guys prefer. I don't want it to be another naming war :))
> and have savan and rampart under that - just like what we have in
> ws-commons right now.
>
> do I make any sense ?
>
> Ajith
>
> [1] http://ws.apache.org/#Project+List
>
> On 8/31/06, Eran Chinthaka <ch...@opensource.lk> wrote:
> > Another big +1 from me too.
> >
> > I was really worried about the increasing number of modules within Axis2
> > project, but didn't take this up as people were busy with other
> > important issues. I'd like to add two more things to Ruchith's proposal.
> >
> > 1. Move Savan also to a sub-project out of Axis2
> >
> > 2. Write some integration tests in Axis2 to compensate the valuable
> > tests Ruchith had written to test the integrity of Axis2 client and
> > server. Whenever you do some random changes in Axis2, security tests
> > were failing as they were the only tests which tested the real
> > integration. Since these tests also will be moved with Rahas and
> > Rampart, we need to have some tests to compensate them
> >
> > 3. Need to have a gump like thingy setup to run all the tests in Axis2
> > and related projects and to bug whoever breaks the total build.
> >
> > Any volunteers?
> >
> > -- Chinthaka
> >
> > Sanjiva Weerawarana wrote:
> > > On Thu, 2006-08-31 at 20:28 +0530, Ruchith Fernando wrote:
> > >> Basically how about pushing these up to be two new sub projects or the
> > >> Apache Web services project :
> > >>
> > >> Ramaprt - WS-Security and WS-SecureConversation implementation
> > >> Rahas - WS-Trust implementation
> > >>
> > >> This is similar to the way we have Sandesha (WS-RM impl), and they
> > >> will have their own release cycles etc. ?
> > >
> > > Big +1 from me. I don't see any need to clutter up WSS4J with all this
> > > stuff - let's keep WSS4J at the level it is and add separate projects to
> > > cover the other functionality (which are Axis2 and Axiom coupled
> > > anyway).
> > >
> > > Sanjiva.
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> >
> >
> >
>
>
> --
> Ajith Ranabahu
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
www.ruchith.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org