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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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: [EMAIL PROTECTED]
> > > > For additional commands, e-mail: [EMAIL PROTECTED]
> > > >
> > > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > Ajith Ranabahu
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
>
> --
> www.ruchith.org
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Ajith Ranabahu
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
