Re: [Ws Wiki] Update of FrontPage/Proposals/Axis2TLPProposal by GlenDaniels

2008-11-03 Thread Asankha Perera

Glen

The following page has been changed by GlenDaniels:
http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal


   RESOLVED, that the Apache Axis2 Project be and hereby
   is tasked with the migration and rationalization of the
   following Apache Web Services sub-projects:
   
 * Axis2/Java

 * Axis2/C
 * Rampart
 * Sandesha
 * Kandula
 * Savan
 * WS-Commons Transports
  
The WS-Commons transports should not belong to an Axis2 TLP - as it has 
a life of its own and is heavily used by Synapse - probably even more 
than by Axis2! Shall I edit the proposal directly to remove this?


asankha

--
Asankha C. Perera
http://adroitlogic.org

http://esbmagic.blogspot.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Ws Wiki] Update of FrontPage/Proposals/Axis2TLPProposal by GlenDaniels

2008-11-03 Thread Davanum Srinivas
Asankha,

I agree. But let's let Glen edit the pages based on consensus.

thanks,
dims

On Mon, Nov 3, 2008 at 10:33 AM, Asankha Perera [EMAIL PROTECTED] wrote:
 Glen

 The following page has been changed by GlenDaniels:
 http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal

 
   RESOLVED, that the Apache Axis2 Project be and hereby
   is tasked with the migration and rationalization of the
   following Apache Web Services sub-projects:
   * Axis2/Java
 * Axis2/C
 * Rampart
 * Sandesha
 * Kandula
 * Savan
 * WS-Commons Transports


 The WS-Commons transports should not belong to an Axis2 TLP - as it has a
 life of its own and is heavily used by Synapse - probably even more than by
 Axis2! Shall I edit the proposal directly to remove this?

 asankha

 --
 Asankha C. Perera
 http://adroitlogic.org

 http://esbmagic.blogspot.com


 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]





-- 
Davanum Srinivas :: http://davanum.wordpress.com

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Ws Wiki] Update of FrontPage/Proposals/Axis2TLPProposal by GlenDaniels

2008-11-03 Thread Glen Daniels

Hi Asankha:

Asankha Perera wrote:

 * WS-Commons Transports
  
The WS-Commons transports should not belong to an Axis2 TLP - as it has 
a life of its own and is heavily used by Synapse - probably even more 
than by Axis2! Shall I edit the proposal directly to remove this?


Does Synapse call these transports directly *outside* an Axis2 code 
path?  I was under the impression that even within Synapse the 
transports are still used as Axis2 plugins and called via Axis2 code... 
if that's the case, then IMO they should in fact live with Axis2 
(because like the Modules, they're components that are only usable 
within the Axis2 framework).  Separate component, independent release 
schedules just like in commons, but I do think if we're going to 
restructure we should take the opportunity to put all the Axis2-specific 
stuff together.


If I'm mistaken, and indeed Synapse DOES call transports directly 
outside of the Axis2 code path, then I think it's somewhat less clear 
cut and we should discuss.


Thanks,
--Glen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Ws Wiki] Update of FrontPage/Proposals/Axis2TLPProposal by GlenDaniels

2008-11-03 Thread Andreas Veithen
Glen,

Synapse uses the transport through Axis2. My point of view has always
been that it makes sense to have the transports in a separate project
(- independent release cycle) but that the most natural solution
would be as a subproject of Axis2, so I completely agree with you on
that point.

Andreas

PS: Glen, can you add a Transports component for WSCOMMONS and check
my access rights in JIRA (I'm not yet in the right group for
WSCOMMONS)?

On Mon, Nov 3, 2008 at 17:53, Glen Daniels [EMAIL PROTECTED] wrote:
 Hi Asankha:

 Asankha Perera wrote:

 * WS-Commons Transports


 The WS-Commons transports should not belong to an Axis2 TLP - as it has a
 life of its own and is heavily used by Synapse - probably even more than by
 Axis2! Shall I edit the proposal directly to remove this?

 Does Synapse call these transports directly *outside* an Axis2 code path?  I
 was under the impression that even within Synapse the transports are still
 used as Axis2 plugins and called via Axis2 code... if that's the case, then
 IMO they should in fact live with Axis2 (because like the Modules, they're
 components that are only usable within the Axis2 framework).  Separate
 component, independent release schedules just like in commons, but I do
 think if we're going to restructure we should take the opportunity to put
 all the Axis2-specific stuff together.

 If I'm mistaken, and indeed Synapse DOES call transports directly outside of
 the Axis2 code path, then I think it's somewhat less clear cut and we should
 discuss.

 Thanks,
 --Glen

 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [Ws Wiki] Update of FrontPage/Proposals/Axis2TLPProposal by GlenDaniels

2008-11-03 Thread Asankha Perera

Glen
 * WS-Commons Transports  
The WS-Commons transports should not belong to an Axis2 TLP - as it 
has a life of its own and is heavily used by Synapse - probably even 
more than by Axis2! Shall I edit the proposal directly to remove this?
Does Synapse call these transports directly *outside* an Axis2 code 
path?  I was under the impression that even within Synapse the 
transports are still used as Axis2 plugins and called via Axis2 
code... if that's the case, then IMO they should in fact live with 
Axis2 (because like the Modules, they're components that are only 
usable within the Axis2 framework).  Separate component, independent 
release schedules just like in commons, but I do think if we're going 
to restructure we should take the opportunity to put all the 
Axis2-specific stuff together.


If I'm mistaken, and indeed Synapse DOES call transports directly 
outside of the Axis2 code path, then I think it's somewhat less clear 
cut and we should discuss.
I just re-read the thread that finally coerced me to let the code that 
was mostly developed by me, out of Synapse : 
http://markmail.org/message/okzimikvmbhimflr


There is nothing else for me to say anymore..

asankha

--
Asankha C. Perera
http://adroitlogic.org

http://esbmagic.blogspot.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]