[prev in list] [next in list] [prev in thread] [next in thread]
List: rampart-dev
Subject: Re: Release Rampart 1.5.1 in sync with Axis2 1.5.4
From: indika kumara <indika.kuma () gmail ! com>
Date: 2010-12-30 16:40:16
Message-ID: AANLkTi=V=aT-0qwO6igKoHCM=31NyvisWKss3vPKdbD- () mail ! gmail ! com
[Download RAW message or body]
I am just curious to know what the main reasons for having separate projects
for the Sandesha, Rampart, Transports, etc. instead of separated modules
inside the axis2. pros and cons? especially considering software qualities
such as cost and schedule, marketability, etc.
As per my knowledge, all those products are tightly coupled with the axis2.
If any other project, for instance the Synapse, needs to use them, that
project needs to use the axis2. There are not reusable in any project that
does not employ the axis2.
Moreover, can an old axis2 binary use a newer rampart binary? For example, a
user only needs to solve a security issue and just needs to update the
security module (here rampart). Is it recommended? Is there a value for a
previously released product or it just becomes obsolete when a newer version
is released?
Thanks,
Indika
On Thu, Dec 30, 2010 at 3:22 PM, Andreas Veithen
<andreas.veithen@gmail.com>wrote:
> If that uber-distribution is something separate from the Axis2 build
> and if we have a volunteer to work on it (so that we can get a better
> idea what this means in practice), then I have no objections.
>
> Andreas
>
> On Thu, Dec 23, 2010 at 04:58, Ruwan Linton <ruwan.linton@gmail.com>
> wrote:
> > I think there is no objection to this, so I will start on this distro as
> a
> > subproject in axis2 on the trunk. I don't think we can get this
> distribution
> > into the axis2 modules without a major structural change, so assume it is
> OK
> > to create a subproject for the distro and have svn externs to the axis2,
> > rampart and sandesha and let them build before building the distro.
> > Thanks,
> > Ruwan
> >
> > On Thu, Dec 23, 2010 at 6:00 AM, Nandana Mihindukulasooriya
> > <nandana.cse@gmail.com> wrote:
> >>
> >> On Wed, Dec 22, 2010 at 4:27 PM, Ruwan Linton <ruwan.linton@gmail.com>
> >> wrote:
> >>>
> >>> Well, even right now, One has to build the distribution module
> separately
> >>> after building the axis2 project from the root pom. So in effect it is
> >>> really a separate thing. I suggest we move the axis2 distribution into
> a
> >>> separate subproject under Axis2. I really think that the Axis2 distro
> should
> >>> have Rampart and Sandesha2 built into it. We can also decide on the
> >>> transports that we need to add by default to this distro with this
> method.
> >>
> >> +1. I am sure it will be much easier for the users to have a distro with
> >> Security & RM built-in rather than downloading them separately and
> >> installing them and they also won't have to worry about which Rampart
> >> version and which Sandesha version work with a given Axis2 version etc.
> >> Best Regards,
> >> Nandana
> >>
> >>>
> >>> On Wed, Dec 22, 2010 at 7:36 PM, Samisa Abeysinghe
> >>> <samisa.abeysinghe@gmail.com> wrote:
> >>>>
> >>>> If it is too many logistics to build one pack, we can have separate
> >>>> packs but release all three at the same time, at least few days apart
> >>>>
> >>>> Samisa...
> >>>>
> >>>> On Wed, Dec 22, 2010 at 6:12 PM, Andreas Veithen
> >>>> <andreas.veithen@gmail.com> wrote:
> >>>>>
> >>>>> This would require again changes to the project structure and/or to
> >>>>> the build and release system. I'm not in principle against this, but
> >>>>> the issue I see with this is the following: In 2009 we moved the
> >>>>> transports into a separate project and in 2010 we migrated to a new
> >>>>> TLP. All this required lots of changes and it took a long time to
> >>>>> complete this (the TLP migration is still not entirely complete). If
> >>>>> we change the project structure every year and every time it takes
> >>>>> months to complete this, then we will never reach a stable situation.
> >>>>>
> >>>>> My counterproposal is to keep things as they are in terms of project
> >>>>> structure, but continue to streamline the release processes. We can
> >>>>> then move to a release early, release often policy (as is happening
> >>>>> right now with the Axis2 1.5 branch) and also have simultaneous
> >>>>> releases (as I did for Sandesha2 and Axis2). This would allow us to
> >>>>> keep the flexibility to postpone the release of one of the
> subprojects
> >>>>> if there are blocking issues.
> >>>>>
> >>>>> To summarize: I think that the real pain point is not that we have
> >>>>> separate subprojects, but that the release cycles are too long. This
> >>>>> can only be solved by making the release process easier, more
> >>>>> predictable and well documented.
> >>>>>
> >>>>> Andreas
> >>>>>
> >>>>> On Wed, Dec 22, 2010 at 05:09, Ruwan Linton <ruwan.linton@gmail.com>
> >>>>> wrote:
> >>>>> > In the future how about bundling Rampart and Sandesha2 into the
> Axis2
> >>>>> > distribution itself? It is really part of Axis2 I guess. The recent
> >>>>> > experience that I had with the Synapse release convinced me that
> >>>>> > Rampart and
> >>>>> > Sandesha2 are really part of Axis2? Why do't we create a one single
> >>>>> > distribution with Rampart and Sandesh2 when we release Axis2.
> >>>>> > May be I am hijacking this thread, but I guess this thread is there
> >>>>> > also
> >>>>> > because of the above issue of separately releasing the Rampart and
> >>>>> > Sandesha2.
> >>>>> > WDYT?
> >>>>> > Thanks,
> >>>>> > Ruwan
> >>>>> >
> >>>>> > On Wed, Dec 22, 2010 at 9:32 AM, Thilina Mahesh Buddhika
> >>>>> > <thilinamb@gmail.com> wrote:
> >>>>> >>
> >>>>> >> On Wed, Dec 22, 2010 at 7:56 AM, Samisa Abeysinghe
> >>>>> >> <samisa.abeysinghe@gmail.com> wrote:
> >>>>> >>>
> >>>>> >>> We have fixed loads of Rampart issues yesterday and we will be
> able
> >>>>> >>> to
> >>>>> >>> fix some more today as well.
> >>>>> >>>
> >>>>> >>> How about a release ASAP? I think users will benefit by having
> >>>>> >>> latest
> >>>>> >>> rampart working with latest Axis2.
> >>>>> >>
> >>>>> >> +1.
> >>>>> >>
> >>>>> >> We can do this release based on the recently released WSS4J
> 1.5.10.
> >>>>> >>
> >>>>> >> Thanks,
> >>>>> >> Thilina
> >>>>> >>
> >>>>> >>>
> >>>>> >>> Samisa...
> >>>>> >>
> >>>>> >
> >>>>> >
> >>>>> >
> >>>>> > --
> >>>>> > Ruwan Linton
> >>>>> > Software Architect & Product Manager, WSO2 ESB;
> http://wso2.org/esb
> >>>>> > WSO2 Inc.; http://wso2.org
> >>>>> >
> >>>>> > Lean . Enterprise . Middleware
> >>>>> >
> >>>>> > phone: +1 408 754 7388 ext 51789
> >>>>> > email: ruwan@wso2.com; cell: +94 77 341 3097
> >>>>> > blog: http://blog.ruwan.org
> >>>>> > linkedin: http://www.linkedin.com/in/ruwanlinton
> >>>>> > google: http://www.google.com/profiles/ruwan.linton
> >>>>> > tweet: http://twitter.com/ruwanlinton
> >>>>> >
> >>>>>
> >>>>> ---------------------------------------------------------------------
> >>>>> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> >>>>> For additional commands, e-mail: java-dev-help@axis.apache.org
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Ruwan Linton
> >>> Software Architect & Product Manager, WSO2 ESB; http://wso2.org/esb
> >>> WSO2 Inc.; http://wso2.org
> >>>
> >>> Lean . Enterprise . Middleware
> >>>
> >>> phone: +1 408 754 7388 ext 51789
> >>> email: ruwan@wso2.com; cell: +94 77 341 3097
> >>> blog: http://blog.ruwan.org
> >>> linkedin: http://www.linkedin.com/in/ruwanlinton
> >>> google: http://www.google.com/profiles/ruwan.linton
> >>> tweet: http://twitter.com/ruwanlinton
> >>
> >
> >
> >
> > --
> > Ruwan Linton
> > Software Architect & Product Manager
> > WSO2 Inc.; http://wso2.org
> >
> > Lean . Enterprise . Middleware
> >
> > phone: +1 408 754 7388 ext 51789
> > email: ruwan@wso2.com; cell: +94 77 341 3097
> > blog: http://blog.ruwan.org
> > linkedin: http://www.linkedin.com/in/ruwanlinton
> > google: http://www.google.com/profiles/ruwan.linton
> > tweet: http://twitter.com/ruwanlinton
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
> For additional commands, e-mail: java-dev-help@axis.apache.org
>
>
[Attachment #3 (text/html)]
I am just curious to know what the main reasons for having separate projects for the \
Sandesha, Rampart, Transports, etc. instead of separated modules inside the axis2. \
pros and cons? especially considering software qualities such as cost and schedule, \
marketability, etc. <br> <br>As per my knowledge, all those products are tightly \
coupled with the axis2. If any other project, for instance the Synapse, needs to use \
them, that project needs to use the axis2. There are not reusable in any project \
that does not employ the axis2.<br> <br>Moreover, can an old axis2 binary use a newer \
rampart binary? For example, a user only needs to solve a security issue and just \
needs to update the security module (here rampart). Is it recommended? Is there a \
value for a previously released product or it just becomes obsolete when a newer \
version is released?<br> <br>Thanks,<br><br>Indika<br><br><div class="gmail_quote">On \
Thu, Dec 30, 2010 at 3:22 PM, Andreas Veithen <span dir="ltr"><<a \
href="mailto:andreas.veithen@gmail.com">andreas.veithen@gmail.com</a>></span> \
wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, \
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">If that uber-distribution \
is something separate from the Axis2 build<br> and if we have a volunteer to work on \
it (so that we can get a better<br> idea what this means in practice), then I have no \
objections.<br> <font color="#888888"><br>
Andreas<br>
</font><div><div></div><div class="h5"><br>
On Thu, Dec 23, 2010 at 04:58, Ruwan Linton <<a \
href="mailto:ruwan.linton@gmail.com">ruwan.linton@gmail.com</a>> wrote:<br> > I \
think there is no objection to this, so I will start on this distro as a<br> > \
subproject in axis2 on the trunk. I don't think we can get this distribution<br> \
> into the axis2 modules without a major structural change, so assume it is OK<br> \
> to create a subproject for the distro and have svn externs to the axis2,<br> \
> rampart and sandesha and let them build before building the distro.<br> > \
Thanks,<br> > Ruwan<br>
><br>
> On Thu, Dec 23, 2010 at 6:00 AM, Nandana Mihindukulasooriya<br>
> <<a href="mailto:nandana.cse@gmail.com">nandana.cse@gmail.com</a>> \
wrote:<br> >><br>
>> On Wed, Dec 22, 2010 at 4:27 PM, Ruwan Linton <<a \
href="mailto:ruwan.linton@gmail.com">ruwan.linton@gmail.com</a>><br> >> \
wrote:<br> >>><br>
>>> Well, even right now, One has to build the distribution module \
separately<br> >>> after building the axis2 project from the root pom. So in \
effect it is<br> >>> really a separate thing. I suggest we move the axis2 \
distribution into a<br> >>> separate subproject under Axis2. I really think \
that the Axis2 distro should<br> >>> have Rampart and Sandesha2 built into \
it. We can also decide on the<br> >>> transports that we need to add by \
default to this distro with this method.<br> >><br>
>> +1. I am sure it will be much easier for the users to have a distro with<br>
>> Security & RM built-in rather than downloading them separately and<br>
>> installing them and they also won't have to worry about which \
Rampart<br> >> version and which Sandesha version work with a given Axis2 \
version etc.<br> >> Best Regards,<br>
>> Nandana<br>
>><br>
>>><br>
>>> On Wed, Dec 22, 2010 at 7:36 PM, Samisa Abeysinghe<br>
>>> <<a href="mailto:samisa.abeysinghe@gmail.com">samisa.abeysinghe@gmail.com</a>> \
wrote:<br> >>>><br>
>>>> If it is too many logistics to build one pack, we can have \
separate<br> >>>> packs but release all three at the same time, at least \
few days apart<br> >>>><br>
>>>> Samisa...<br>
>>>><br>
>>>> On Wed, Dec 22, 2010 at 6:12 PM, Andreas Veithen<br>
>>>> <<a \
href="mailto:andreas.veithen@gmail.com">andreas.veithen@gmail.com</a>> wrote:<br> \
>>>>><br> >>>>> This would require again changes to the \
project structure and/or to<br> >>>>> the build and release system. \
I'm not in principle against this, but<br> >>>>> the issue I see \
with this is the following: In 2009 we moved the<br> >>>>> transports \
into a separate project and in 2010 we migrated to a new<br> >>>>> \
TLP. All this required lots of changes and it took a long time to<br> \
>>>>> complete this (the TLP migration is still not entirely \
complete). If<br> >>>>> we change the project structure every year and \
every time it takes<br> >>>>> months to complete this, then we will \
never reach a stable situation.<br> >>>>><br>
>>>>> My counterproposal is to keep things as they are in terms of \
project<br> >>>>> structure, but continue to streamline the release \
processes. We can<br> >>>>> then move to a release early, release \
often policy (as is happening<br> >>>>> right now with the Axis2 1.5 \
branch) and also have simultaneous<br> >>>>> releases (as I did for \
Sandesha2 and Axis2). This would allow us to<br> >>>>> keep the \
flexibility to postpone the release of one of the subprojects<br> \
>>>>> if there are blocking issues.<br> >>>>><br>
>>>>> To summarize: I think that the real pain point is not that we \
have<br> >>>>> separate subprojects, but that the release cycles are \
too long. This<br> >>>>> can only be solved by making the release \
process easier, more<br> >>>>> predictable and well documented.<br>
>>>>><br>
>>>>> Andreas<br>
>>>>><br>
>>>>> On Wed, Dec 22, 2010 at 05:09, Ruwan Linton <<a \
href="mailto:ruwan.linton@gmail.com">ruwan.linton@gmail.com</a>><br> \
>>>>> wrote:<br> >>>>> > In the future how about \
bundling Rampart and Sandesha2 into the Axis2<br> >>>>> > \
distribution itself? It is really part of Axis2 I guess. The recent<br> \
>>>>> > experience that I had with the Synapse release convinced me \
that<br> >>>>> > Rampart and<br>
>>>>> > Sandesha2 are really part of Axis2? Why do't we create \
a one single<br> >>>>> > distribution with Rampart and Sandesh2 \
when we release Axis2.<br> >>>>> > May be I am hijacking this \
thread, but I guess this thread is there<br> >>>>> > also<br>
>>>>> > because of the above issue of separately releasing the \
Rampart and<br> >>>>> > Sandesha2.<br>
>>>>> > WDYT?<br>
>>>>> > Thanks,<br>
>>>>> > Ruwan<br>
>>>>> ><br>
>>>>> > On Wed, Dec 22, 2010 at 9:32 AM, Thilina Mahesh \
Buddhika<br> >>>>> > <<a \
href="mailto:thilinamb@gmail.com">thilinamb@gmail.com</a>> wrote:<br> \
>>>>> >><br> >>>>> >> On Wed, Dec 22, 2010 \
at 7:56 AM, Samisa Abeysinghe<br> >>>>> >> <<a \
href="mailto:samisa.abeysinghe@gmail.com">samisa.abeysinghe@gmail.com</a>> \
wrote:<br> >>>>> >>><br>
>>>>> >>> We have fixed loads of Rampart issues yesterday and \
we will be able<br> >>>>> >>> to<br>
>>>>> >>> fix some more today as well.<br>
>>>>> >>><br>
>>>>> >>> How about a release ASAP? I think users will \
benefit by having<br> >>>>> >>> latest<br>
>>>>> >>> rampart working with latest Axis2.<br>
>>>>> >><br>
>>>>> >> +1.<br>
>>>>> >><br>
>>>>> >> We can do this release based on the recently released \
WSS4J 1.5.10.<br> >>>>> >><br>
>>>>> >> Thanks,<br>
>>>>> >> Thilina<br>
>>>>> >><br>
>>>>> >>><br>
>>>>> >>> Samisa...<br>
>>>>> >><br>
>>>>> ><br>
>>>>> ><br>
>>>>> ><br>
>>>>> > --<br>
>>>>> > Ruwan Linton<br>
>>>>> > Software Architect & Product Manager, WSO2 ESB; <a \
href="http://wso2.org/esb" target="_blank">http://wso2.org/esb</a><br> \
>>>>> > WSO2 Inc.; <a href="http://wso2.org" \
target="_blank">http://wso2.org</a><br> >>>>> ><br>
>>>>> > Lean . Enterprise . Middleware<br>
>>>>> ><br>
>>>>> > phone: +1 408 754 7388 ext 51789<br>
>>>>> > email: <a href="mailto:ruwan@wso2.com">ruwan@wso2.com</a>; \
cell: +94 77 341 3097<br> >>>>> > blog: <a \
href="http://blog.ruwan.org" target="_blank">http://blog.ruwan.org</a><br> \
>>>>> > linkedin: <a href="http://www.linkedin.com/in/ruwanlinton" \
target="_blank">http://www.linkedin.com/in/ruwanlinton</a><br> >>>>> \
> google: <a href="http://www.google.com/profiles/ruwan.linton" \
target="_blank">http://www.google.com/profiles/ruwan.linton</a><br> \
>>>>> > tweet: <a href="http://twitter.com/ruwanlinton" \
target="_blank">http://twitter.com/ruwanlinton</a><br> >>>>> ><br>
>>>>><br>
>>>>> \
---------------------------------------------------------------------<br> \
>>>>> To unsubscribe, e-mail: <a \
href="mailto:java-dev-unsubscribe@axis.apache.org">java-dev-unsubscribe@axis.apache.org</a><br>
>>>>> For additional commands, e-mail: <a \
href="mailto:java-dev-help@axis.apache.org">java-dev-help@axis.apache.org</a><br> \
>>>>><br> >>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> Ruwan Linton<br>
>>> Software Architect & Product Manager, WSO2 ESB; <a \
href="http://wso2.org/esb" target="_blank">http://wso2.org/esb</a><br> >>> \
WSO2 Inc.; <a href="http://wso2.org" target="_blank">http://wso2.org</a><br> \
>>><br> >>> Lean . Enterprise . Middleware<br>
>>><br>
>>> phone: +1 408 754 7388 ext 51789<br>
>>> email: <a href="mailto:ruwan@wso2.com">ruwan@wso2.com</a>; cell: +94 77 \
341 3097<br> >>> blog: <a href="http://blog.ruwan.org" \
target="_blank">http://blog.ruwan.org</a><br> >>> linkedin: <a \
href="http://www.linkedin.com/in/ruwanlinton" \
target="_blank">http://www.linkedin.com/in/ruwanlinton</a><br> >>> google: \
<a href="http://www.google.com/profiles/ruwan.linton" \
target="_blank">http://www.google.com/profiles/ruwan.linton</a><br> >>> \
tweet: <a href="http://twitter.com/ruwanlinton" \
target="_blank">http://twitter.com/ruwanlinton</a><br> >><br>
><br>
><br>
><br>
> --<br>
> Ruwan Linton<br>
> Software Architect & Product Manager<br>
> WSO2 Inc.; <a href="http://wso2.org" target="_blank">http://wso2.org</a><br>
><br>
> Lean . Enterprise . Middleware<br>
><br>
> phone: +1 408 754 7388 ext 51789<br>
> email: <a href="mailto:ruwan@wso2.com">ruwan@wso2.com</a>; cell: +94 77 341 \
3097<br> > blog: <a href="http://blog.ruwan.org" \
target="_blank">http://blog.ruwan.org</a><br> > linkedin: <a \
href="http://www.linkedin.com/in/ruwanlinton" \
target="_blank">http://www.linkedin.com/in/ruwanlinton</a><br> > google: <a \
href="http://www.google.com/profiles/ruwan.linton" \
target="_blank">http://www.google.com/profiles/ruwan.linton</a><br> > tweet: <a \
href="http://twitter.com/ruwanlinton" \
target="_blank">http://twitter.com/ruwanlinton</a><br> ><br>
<br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a \
href="mailto:java-dev-unsubscribe@axis.apache.org">java-dev-unsubscribe@axis.apache.org</a><br>
For additional commands, e-mail: <a \
href="mailto:java-dev-help@axis.apache.org">java-dev-help@axis.apache.org</a><br> \
<br> </div></div></blockquote></div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic