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 Srinath Perera <he...@gmail.com> on 2005/03/04 03:42:37 UTC
[Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
This is to follow up "Should we create a Transport module?" thread. We
got in to two major options for modularizing the trnsports. Since we
do not decide which to choose .. I would Like to call for a vote
1) one modules for all the transports
2) A module for each transport
I slightly favours the #1, but fine with the both! ... so +1 for #1
Thanks
Srinath
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
Posted by Srinath Perera <he...@gmail.com>.
mm .. accroding to votes it is 3/2 in the favour of transport module
for each transport,
BTW regarding Davids sugesstion for transports .. am too not sure does
the transports that high level part of axis?
Then shall I go ahead with the module for each transport .. it is
onhold for about a week now Thanks
Srinath
On Sat, 5 Mar 2005 02:15:44 +0600, Sanjiva Weerawarana
<sa...@opensource.lk> wrote:
> Yeah this is the jar classloader thing right? I saw that too ... but
> I'd prefer for us to package into one jar period.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Aleksander Slominski" <as...@cs.indiana.edu>
> To: <ax...@ws.apache.org>
> Cc: "Srinath Perera" <he...@gmail.com>
> Sent: Friday, March 04, 2005 10:27 PM
> Subject: Re: [Axis2][Vote]How to modularize the transports?[Followup:Should
> we create a Transport module?]
>
> > Sanjiva Weerawarana wrote:
> >
> > >+1 for (2). IMO people will use one or at most a few transports
> > >at any given time and being able to build just those will be
> > >good.
> > >
> > >At the same time I don't want to end up with the Axis1 "jar hell"
> > >and end up with 20 jars that have to be added. I'd like to explore
> > >the possibility of keeping them as separate modules but at some
> > >point (after building) being able to combine stuff into a single
> > >jar.
> > >
> > >
> > i have seen one interesting idea to do it especially useful on client
> side:
> > http://one-jar.sourceforge.net/
> > http://www-106.ibm.com/developerworks/library/j-onejar/
> >
> > alek
> >
> > >
> > >----- Original Message -----
> > >From: "Srinath Perera" <he...@gmail.com>
> > >To: <ax...@ws.apache.org>
> > >Sent: Friday, March 04, 2005 8:42 AM
> > >Subject: [Axis2][Vote]How to modularize the transports?[Followup:Should
> we
> > >create a Transport module?]
> > >
> > >
> > >
> > >
> > >>This is to follow up "Should we create a Transport module?" thread. We
> > >>got in to two major options for modularizing the trnsports. Since we
> > >>do not decide which to choose .. I would Like to call for a vote
> > >>1) one modules for all the transports
> > >>2) A module for each transport
> > >>
> > >>I slightly favours the #1, but fine with the both! ... so +1 for #1
> > >>Thanks
> > >>Srinath
> > >>
> > >>
> > >>
> > >
> > >
> > >
> >
> >
> > --
> > The best way to predict the future is to invent it - Alan Kay
> >
> >
>
>
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Yeah this is the jar classloader thing right? I saw that too ... but
I'd prefer for us to package into one jar period.
Sanjiva.
----- Original Message -----
From: "Aleksander Slominski" <as...@cs.indiana.edu>
To: <ax...@ws.apache.org>
Cc: "Srinath Perera" <he...@gmail.com>
Sent: Friday, March 04, 2005 10:27 PM
Subject: Re: [Axis2][Vote]How to modularize the transports?[Followup:Should
we create a Transport module?]
> Sanjiva Weerawarana wrote:
>
> >+1 for (2). IMO people will use one or at most a few transports
> >at any given time and being able to build just those will be
> >good.
> >
> >At the same time I don't want to end up with the Axis1 "jar hell"
> >and end up with 20 jars that have to be added. I'd like to explore
> >the possibility of keeping them as separate modules but at some
> >point (after building) being able to combine stuff into a single
> >jar.
> >
> >
> i have seen one interesting idea to do it especially useful on client
side:
> http://one-jar.sourceforge.net/
> http://www-106.ibm.com/developerworks/library/j-onejar/
>
> alek
>
> >
> >----- Original Message -----
> >From: "Srinath Perera" <he...@gmail.com>
> >To: <ax...@ws.apache.org>
> >Sent: Friday, March 04, 2005 8:42 AM
> >Subject: [Axis2][Vote]How to modularize the transports?[Followup:Should
we
> >create a Transport module?]
> >
> >
> >
> >
> >>This is to follow up "Should we create a Transport module?" thread. We
> >>got in to two major options for modularizing the trnsports. Since we
> >>do not decide which to choose .. I would Like to call for a vote
> >>1) one modules for all the transports
> >>2) A module for each transport
> >>
> >>I slightly favours the #1, but fine with the both! ... so +1 for #1
> >>Thanks
> >>Srinath
> >>
> >>
> >>
> >
> >
> >
>
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
>
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should
we create a Transport module?]
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Sanjiva Weerawarana wrote:
>+1 for (2). IMO people will use one or at most a few transports
>at any given time and being able to build just those will be
>good.
>
>At the same time I don't want to end up with the Axis1 "jar hell"
>and end up with 20 jars that have to be added. I'd like to explore
>the possibility of keeping them as separate modules but at some
>point (after building) being able to combine stuff into a single
>jar.
>
>
i have seen one interesting idea to do it especially useful on client side:
http://one-jar.sourceforge.net/
http://www-106.ibm.com/developerworks/library/j-onejar/
alek
>
>----- Original Message -----
>From: "Srinath Perera" <he...@gmail.com>
>To: <ax...@ws.apache.org>
>Sent: Friday, March 04, 2005 8:42 AM
>Subject: [Axis2][Vote]How to modularize the transports?[Followup:Should we
>create a Transport module?]
>
>
>
>
>>This is to follow up "Should we create a Transport module?" thread. We
>>got in to two major options for modularizing the trnsports. Since we
>>do not decide which to choose .. I would Like to call for a vote
>>1) one modules for all the transports
>>2) A module for each transport
>>
>>I slightly favours the #1, but fine with the both! ... so +1 for #1
>>Thanks
>>Srinath
>>
>>
>>
>
>
>
--
The best way to predict the future is to invent it - Alan Kay
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1 for (2). IMO people will use one or at most a few transports
at any given time and being able to build just those will be
good.
At the same time I don't want to end up with the Axis1 "jar hell"
and end up with 20 jars that have to be added. I'd like to explore
the possibility of keeping them as separate modules but at some
point (after building) being able to combine stuff into a single
jar.
Sanjiva.
----- Original Message -----
From: "Srinath Perera" <he...@gmail.com>
To: <ax...@ws.apache.org>
Sent: Friday, March 04, 2005 8:42 AM
Subject: [Axis2][Vote]How to modularize the transports?[Followup:Should we
create a Transport module?]
> This is to follow up "Should we create a Transport module?" thread. We
> got in to two major options for modularizing the trnsports. Since we
> do not decide which to choose .. I would Like to call for a vote
> 1) one modules for all the transports
> 2) A module for each transport
>
> I slightly favours the #1, but fine with the both! ... so +1 for #1
> Thanks
> Srinath
>
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
Posted by Ajith Ranabahu <aj...@gmail.com>.
Hi,
Hate to say this guys but I'm 0- on having seperate transport modules.
It's my desire to see a transport module and everything on transports
squeezed into that.
On Fri, 4 Mar 2005 15:03:37 +0600, Eran Chinthaka
<ch...@opensource.lk> wrote:
> Well, I'm 0+ for module for each transport, as its easier for module
> developers.
>
> But will this add too many modules ??
>
> Chinthaka
>
> -----Original Message-----
> From: Aleksander Slominski [mailto:aslom@cs.indiana.edu]
> Sent: Friday, March 04, 2005 1:21 PM
> To: axis-dev@ws.apache.org
> Subject: Re: [Axis2][Vote]How to modularize the transports?[Followup:Should
> we create a Transport module?]
>
> Srinath Perera wrote:
>
> >This is to follow up "Should we create a Transport module?" thread. We
> >got in to two major options for modularizing the trnsports. Since we
> >do not decide which to choose .. I would Like to call for a vote
> >1) one modules for all the transports
> >2) A module for each transport
> >
> >
> +1 for module for each transport
>
> that makes it easier to build axis with set of modules that has required
> functionality and no more or less ;-)
>
> alek
>
> >I slightly favours the #1, but fine with the both! ... so +1 for #1
> >Thanks
> >Srinath
> >
> >
>
> --
> The best way to predict the future is to invent it - Alan Kay
>
>
--
Ajith Ranabahu
RE: [Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
Posted by Eran Chinthaka <ch...@opensource.lk>.
Well, I'm 0+ for module for each transport, as its easier for module
developers.
But will this add too many modules ??
Chinthaka
-----Original Message-----
From: Aleksander Slominski [mailto:aslom@cs.indiana.edu]
Sent: Friday, March 04, 2005 1:21 PM
To: axis-dev@ws.apache.org
Subject: Re: [Axis2][Vote]How to modularize the transports?[Followup:Should
we create a Transport module?]
Srinath Perera wrote:
>This is to follow up "Should we create a Transport module?" thread. We
>got in to two major options for modularizing the trnsports. Since we
>do not decide which to choose .. I would Like to call for a vote
>1) one modules for all the transports
>2) A module for each transport
>
>
+1 for module for each transport
that makes it easier to build axis with set of modules that has required
functionality and no more or less ;-)
alek
>I slightly favours the #1, but fine with the both! ... so +1 for #1
>Thanks
>Srinath
>
>
--
The best way to predict the future is to invent it - Alan Kay
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should
we create a Transport module?]
Posted by Aleksander Slominski <as...@cs.indiana.edu>.
Srinath Perera wrote:
>This is to follow up "Should we create a Transport module?" thread. We
>got in to two major options for modularizing the trnsports. Since we
>do not decide which to choose .. I would Like to call for a vote
>1) one modules for all the transports
>2) A module for each transport
>
>
+1 for module for each transport
that makes it easier to build axis with set of modules that has required functionality and no more or less ;-)
alek
>I slightly favours the #1, but fine with the both! ... so +1 for #1
>Thanks
>Srinath
>
>
--
The best way to predict the future is to invent it - Alan Kay
Re: [Axis2][Vote]How to modularize the transports?[Followup:Should we create a Transport module?]
Posted by David Jencks <dj...@apache.org>.
I'd recommend
modules/core
/etc
transports/http
/jms
/smtp
/etc
however, this isn't too hard to reorganize later if you start with one
transport module and decide to split it up later.
david jencks
On Mar 3, 2005, at 6:42 PM, Srinath Perera wrote:
> This is to follow up "Should we create a Transport module?" thread. We
> got in to two major options for modularizing the trnsports. Since we
> do not decide which to choose .. I would Like to call for a vote
> 1) one modules for all the transports
> 2) A module for each transport
>
> I slightly favours the #1, but fine with the both! ... so +1 for #1
> Thanks
> Srinath
>