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 Davanum Srinivas <da...@gmail.com> on 2008/04/22 14:32:00 UTC
[Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into
Synapse
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Folks,
Let's move JMS and Async NIO transports out of Axis2 into Synapse. There's no point keeping a stale copy in Axis2.
WDYT?
Thanks,
dims
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
nJ5rX+dn2iaC7Fs9/+C+1LE=
=/TIB
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Deepal jayasinghe <de...@gmail.com>.
Glen Daniels wrote:
> -1 from me to move them to Synapse.
>
> These transports (JMS, NIO, whatever) are going to be generally useful
to any Axis2 user, so why make them go look in Synapse's codebase for
them? I agree there should be a single place for them, but that place
should be in Axis2, not somewhere else.
>
I agree with Glen , that we need to keep that in Axis2 not in Synapse.
If it is available in Axis2 then it is automatically available for Synapse.
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Paul Fremantle <pz...@gmail.com>.
+1 to this proposal
Paul
On Wed, Apr 23, 2008 at 5:11 AM, Sanjiva Weerawarana
<sa...@opensource.lk> wrote:
> Wow, miss this list for a few days and boom!
>
> Here's my attempt at a summary position:
>
> - First of all, Asankha, why "synapse-transports.jar"?? That makes no sense
> to me- so if you have a bug in the VFS code you'll rev all the stuff? Why?
> There should be one jar per transport. Yes, lots of jar files but so what?
>
> - Asankha, you seem to think that the only place transports that Synapse
> finds interesting are being done is in Synapse. What about CORBA? The code
> is in Axis2 (and Eranga is still waiting for his commit rights to come thru
> to finish that off) and of course supporting CORBA is very interesting for
> Synapse. So you're not solving whatever problem you perceive by saying "keep
> everything I care about in Synapse."
>
> - I agree with that Axis2 transports should NOT be in the kernel jar. Can
> we finally agree (forget the history please) to that now and create new
> maven modules for each transport and put each one into its own jar? This is
> for the transports that are (or will remain) in ws/axis2.
>
> - Given that these transports are usable by anyone building on Axis2 (and
> not just Synapse) and that they depend on Axis2 APIs, I believe they should
> be in a project which releases those transports against given versions of
> Axis2 APIs. My preference is that it should be in ws/commons/transports or a
> new sub-project called ws/transports. Asankha, what problem do you see in
> that approach? I think everyone would +1 you being the RM for this project
> ;-).
>
> - Asankha if you're going to stick a strong -1 in the middle of this debate
> then I'm going to stick a strong -1 against the status quo of Synapse
> maintaining its own transports. I think the rules now call for us to keep
> talking ;-) ..
>
> - How about the following compromise position:
> - we create a new ws/transports project and move http and any other
> transports out of axis2 into that.
> - we kill the old NHTTP and JMS tranports in axis2
> - move JMS and SMTP out of synapse into the new project
> - as a general rule, if Axis2 and Synapse are both going to ship the
> transport in their default distros, then we move the code here
> - for other transports we strongly encourage people to put them here to
> enable easier wider use (e.g., WSO2 Mashup Server would inherit all the
> transports in Axis2 but not those from Synapse .. I think Asankha would want
> the new and improved SMTP transport to be in the WSO2 Mashup Server too
> ;-)). Of course we can't enforce that but I would hope that we should be
> able to come to a sufficient community understanding between the Synapse and
> WS TLPs to make that work.
> - this project publishes each transport as a separate jar with a naming
> convention that identifies the axis2 (API) version it corresponds to. of
> course trunk will correspond to trunk as always
> - I'm ok with going one step further and even moving the Axis2 transport
> APIs into the project and for Axis2 to just use them. This is like what
> Axis2 does with Axiom for example.
>
> The result is that the transports become an enabler for Axis2 (and Synapse
> and more) just as much as Axiom or XMLSchema is. The benefit is that they're
> no longer "Axis2's transports" or "Synapse's transports" but rather "those
> common transports". (I have to admit I didn't look at the code to evaluate
> the realisticness of this bit of the proposal - but the rest of it stands on
> its own anyway.)
>
> Sanjiva.
>
> Asankha C. Perera wrote:
>
> >
> >
> >
> >
> > Davanum Srinivas wrote:
> >
> > > Agreed that this is definitely a problem.
> > >
> > > Next question, is do you want do this in Synapse Commons (do you have
> one?) or WS Commons?
> > >
> > We already have all the transports in a separate Maven module, which is
> published to Apache snapshots and Central repo.. As far as I am concerned,
> > there is no requirement to re-package this code and ship it elsewhere.. If
> a user wants a particular transport as a separate module, they can ask for
> an enhancement for it, and we will do our best to facilitate it.
> >
> > So if we are going to have a vote on this 'topic' on axis-dev, I am +1 to
> deleting the stale copies of the transports currently in Axis2.
> >
> > But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to make it
> easier for axis2 users to "get" these transports, I'm definitely -1
> >
> > asankha
> >
> > ---------------------------------------------------------------------
> >
> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Paul Fremantle <pz...@gmail.com>.
+1 to this proposal
Paul
On Wed, Apr 23, 2008 at 5:11 AM, Sanjiva Weerawarana
<sa...@opensource.lk> wrote:
> Wow, miss this list for a few days and boom!
>
> Here's my attempt at a summary position:
>
> - First of all, Asankha, why "synapse-transports.jar"?? That makes no sense
> to me- so if you have a bug in the VFS code you'll rev all the stuff? Why?
> There should be one jar per transport. Yes, lots of jar files but so what?
>
> - Asankha, you seem to think that the only place transports that Synapse
> finds interesting are being done is in Synapse. What about CORBA? The code
> is in Axis2 (and Eranga is still waiting for his commit rights to come thru
> to finish that off) and of course supporting CORBA is very interesting for
> Synapse. So you're not solving whatever problem you perceive by saying "keep
> everything I care about in Synapse."
>
> - I agree with that Axis2 transports should NOT be in the kernel jar. Can
> we finally agree (forget the history please) to that now and create new
> maven modules for each transport and put each one into its own jar? This is
> for the transports that are (or will remain) in ws/axis2.
>
> - Given that these transports are usable by anyone building on Axis2 (and
> not just Synapse) and that they depend on Axis2 APIs, I believe they should
> be in a project which releases those transports against given versions of
> Axis2 APIs. My preference is that it should be in ws/commons/transports or a
> new sub-project called ws/transports. Asankha, what problem do you see in
> that approach? I think everyone would +1 you being the RM for this project
> ;-).
>
> - Asankha if you're going to stick a strong -1 in the middle of this debate
> then I'm going to stick a strong -1 against the status quo of Synapse
> maintaining its own transports. I think the rules now call for us to keep
> talking ;-) ..
>
> - How about the following compromise position:
> - we create a new ws/transports project and move http and any other
> transports out of axis2 into that.
> - we kill the old NHTTP and JMS tranports in axis2
> - move JMS and SMTP out of synapse into the new project
> - as a general rule, if Axis2 and Synapse are both going to ship the
> transport in their default distros, then we move the code here
> - for other transports we strongly encourage people to put them here to
> enable easier wider use (e.g., WSO2 Mashup Server would inherit all the
> transports in Axis2 but not those from Synapse .. I think Asankha would want
> the new and improved SMTP transport to be in the WSO2 Mashup Server too
> ;-)). Of course we can't enforce that but I would hope that we should be
> able to come to a sufficient community understanding between the Synapse and
> WS TLPs to make that work.
> - this project publishes each transport as a separate jar with a naming
> convention that identifies the axis2 (API) version it corresponds to. of
> course trunk will correspond to trunk as always
> - I'm ok with going one step further and even moving the Axis2 transport
> APIs into the project and for Axis2 to just use them. This is like what
> Axis2 does with Axiom for example.
>
> The result is that the transports become an enabler for Axis2 (and Synapse
> and more) just as much as Axiom or XMLSchema is. The benefit is that they're
> no longer "Axis2's transports" or "Synapse's transports" but rather "those
> common transports". (I have to admit I didn't look at the code to evaluate
> the realisticness of this bit of the proposal - but the rest of it stands on
> its own anyway.)
>
> Sanjiva.
>
> Asankha C. Perera wrote:
>
> >
> >
> >
> >
> > Davanum Srinivas wrote:
> >
> > > Agreed that this is definitely a problem.
> > >
> > > Next question, is do you want do this in Synapse Commons (do you have
> one?) or WS Commons?
> > >
> > We already have all the transports in a separate Maven module, which is
> published to Apache snapshots and Central repo.. As far as I am concerned,
> > there is no requirement to re-package this code and ship it elsewhere.. If
> a user wants a particular transport as a separate module, they can ask for
> an enhancement for it, and we will do our best to facilitate it.
> >
> > So if we are going to have a vote on this 'topic' on axis-dev, I am +1 to
> deleting the stale copies of the transports currently in Axis2.
> >
> > But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to make it
> easier for axis2 users to "get" these transports, I'm definitely -1
> >
> > asankha
> >
> > ---------------------------------------------------------------------
> >
> > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
> >
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hey Asankha:
Just wanted to quickly reply to this.
Asankha C. Perera wrote:
> So if we are going to have a vote on this 'topic' on axis-dev, I am +1
> to deleting the stale copies of the transports currently in Axis2.
+1, for sure.
> But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to make
> it easier for axis2 users to "get" these transports, I'm definitely -1
I'm "not" exactly sure what the "quotes" mean here :), but I think you
might be looking at this the wrong way. It's not that anyone wants to
wrest control of your code from you - it's that we want to put things
where they make sense. Axiom (or Neethi) is just as critical to Synapse
as any of these transports, and that's in WS-Commons - do you want that
in Synapse too? You, Asankha, as a WS-Commons committer, have exactly
as much control over the code there as you do the code in Synapse, and
of course the devs that have done the work on these up until now will
continue to work on them wherever they live.
Are you not actually interested in making it easy for Axis2 users to
obtain and use these transports?
Anyway, I think I've made my points in the other mails already; I hope
you'll step back a bit and consider. Honestly, as long as there's a
separate transports area with individual transports releasable on their
own, I don't *really* care all that much where it is - but it does seem
to me that it makes more sense in commons than it does in Synapse, for
all the transports that are usable in both contexts.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Asankha C. Perera wrote:
> Deepal
>> As we discussed in the mailing list I created a prototype deployer
>> (TransportDeployer) for transport deployment..
> This is cool and boy you are fast :-) !..
Very cool indeed!
> Axis2 transports also needs a few more changes though.. and I'm
> re-thinking about the suggestion made by Sanjiva on moving the core
> API's out of Axis2 as well.. for example, TransportSender needs a
> start() method, just like the Listeners, as there can be Senders that
> requires initialization, and explicit start/stop behavior.. Else, at
> ConfigurationContext creation itself, the Senders "start" through the
> init() call which is not what you want.. also if you stop a transport,
> you cannot restart.. Another example is with the AxisServlet listener
> which must handle its stop() call etc, and refuse to handle any
> messages through Axis2 if the transport was shutdown.. else if a service
> does not implement the ServiceLifeCycle interface, it may still be
> accessible over the servlet transport even if the lister manager was
> shutdown etc..
>
> So I think its better to *first* work on moving out the current
> transports from Axis2 as proposed, so that we can focus and review the
> transports and the design again, and make any improvements for issues we
> see. I do not think this is something we could try to do in a hurry.. we
> should also focus on good API documentation that will help anyone write
> a new transport easily etc
+1. Let's get the current code moved and restructured and *then* start
improving it.
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Deepal
> As we discussed in the mailing list I created a prototype deployer
> (TransportDeployer) for transport deployment..
This is cool and boy you are fast :-) !..
Axis2 transports also needs a few more changes though.. and I'm
re-thinking about the suggestion made by Sanjiva on moving the core
API's out of Axis2 as well.. for example, TransportSender needs a
start() method, just like the Listeners, as there can be Senders that
requires initialization, and explicit start/stop behavior.. Else, at
ConfigurationContext creation itself, the Senders "start" through the
init() call which is not what you want.. also if you stop a transport,
you cannot restart.. Another example is with the AxisServlet listener
which must handle its stop() call etc, and refuse to handle any
messages through Axis2 if the transport was shutdown.. else if a service
does not implement the ServiceLifeCycle interface, it may still be
accessible over the servlet transport even if the lister manager was
shutdown etc..
So I think its better to *first* work on moving out the current
transports from Axis2 as proposed, so that we can focus and review the
transports and the design again, and make any improvements for issues we
see. I do not think this is something we could try to do in a hurry.. we
should also focus on good API documentation that will help anyone write
a new transport easily etc
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Deepal Jayasinghe <de...@opensource.lk>.
As we discussed in the mailing list I created a prototype deployer
(TransportDeployer) for transport deployment. With the deployer I wrote
we can deploy transport as we deploy service or module. The only thing
we need to do is to add a descriptor file called “transport.xml” into
the META-INF directory of the transport jar file. Then axis2 will read
the xml file and populate the transport. One such an xml file can have
any number of transport senders and receivers. So sample tarnsport.xml
would look like below;
<transports>
<transportSender name="tcp"
class="org.apache.axis2.transport.tcp.TCPTransportSender"/>
<transportSender name="local"
class="org.apache.axis2.transport.local.LocalTransportSender"/>
<transportReceiver name="http"
class="org.apache.axis2.transport.http.SimpleHTTPServer">
<parameter name="port">8080</parameter>
</transportReceiver>
</transports>
If you want your transport to be auto start then add the following
parameter to the transportReceiver.
<parameter name=”AutoStart”>true</parameter>
Thank you!
Deepal
>
> Exactly!
>
> --Glen
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Deepal Jayasinghe wrote:
>> And while we're at it (separate conversation though), perhaps
>> transports should be deployable as easily as services/modules...
>>
>> conf/
>> modules/
>> services/
>> transports/
>> nhttp.tsp
>> jms.tsp
>>
>> ...with transport.xml inside *.tsp/META-INF
>
> This is just a matter of writing a new Deployer :)
> - Read the archive file
> - populate the transport
> - initialize if it needed
> - add to AxisConfiguration
Exactly!
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Deepal Jayasinghe <de...@opensource.lk>.
>
> +1
>
> And while we're at it (separate conversation though), perhaps
> transports should be deployable as easily as services/modules...
>
> conf/
> modules/
> services/
> transports/
> nhttp.tsp
> jms.tsp
>
> ...with transport.xml inside *.tsp/META-INF
This is just a matter of writing a new Deployer :)
- Read the archive file
- populate the transport
- initialize if it needed
- add to AxisConfiguration
Thanks
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hey Sanjiva:
Sanjiva Weerawarana wrote:
> - I agree with that Axis2 transports should NOT be in the kernel jar.
> Can we finally agree (forget the history please) to that now and create
> new maven modules for each transport and put each one into its own jar?
> This is for the transports that are (or will remain) in ws/axis2.
+1
And while we're at it (separate conversation though), perhaps transports
should be deployable as easily as services/modules...
conf/
modules/
services/
transports/
nhttp.tsp
jms.tsp
...with transport.xml inside *.tsp/META-INF
> - Given that these transports are usable by anyone building on Axis2
> (and not just Synapse) and that they depend on Axis2 APIs, I believe
> they should be in a project which releases those transports against
> given versions of Axis2 APIs. My preference is that it should be in
> ws/commons/transports or a new sub-project called ws/transports.
> Asankha, what problem do you see in that approach? I think everyone
> would +1 you being the RM for this project ;-).
Sounds like a plan. :)
See http://markmail.org/message/huukx25f3vgpethi - you might not have
seen that due to the lack of [axis2] prefix.
> - How about the following compromise position:
> - we create a new ws/transports project and move http and any other
> transports out of axis2 into that.
New mailing lists, then? (oh joy more folders :)) I could be ok with
this, but I think using commons is simpler.
> - we kill the old NHTTP and JMS tranports in axis2
Dims is already on this.
> - move JMS and SMTP out of synapse into the new project
+1. We should look at which if any of the Synapse transports are not
generally applicable outside the Synapse context, and move all the others.
> - as a general rule, if Axis2 and Synapse are both going to ship the
> transport in their default distros, then we move the code here
I'd tweak that - as a general rule, if the transport is generally useful
to both projects, it should live here to make sure it gets tested in
both contexts.
> - for other transports we strongly encourage people to put them here
> to enable easier wider use (e.g., WSO2 Mashup Server would inherit all
> the transports in Axis2 but not those from Synapse .. I think Asankha
> would want the new and improved SMTP transport to be in the WSO2 Mashup
> Server too ;-)). Of course we can't enforce that but I would hope that
> we should be able to come to a sufficient community understanding
> between the Synapse and WS TLPs to make that work.
+1
> - this project publishes each transport as a separate jar with a
> naming convention that identifies the axis2 (API) version it corresponds
> to. of course trunk will correspond to trunk as always
Need to think about that a bit.
> - I'm ok with going one step further and even moving the Axis2
> transport APIs into the project and for Axis2 to just use them. This is
> like what Axis2 does with Axiom for example.
+1, yup.
> The result is that the transports become an enabler for Axis2 (and
> Synapse and more) just as much as Axiom or XMLSchema is. The benefit is
> that they're no longer "Axis2's transports" or "Synapse's transports"
> but rather "those common transports". (I have to admit I didn't look at
> the code to evaluate the realisticness of this bit of the proposal - but
> the rest of it stands on its own anyway.)
Well, they ARE still Axis2 transports in that they exist to extend Axis2
- they're just in a common place so other users of Axis2 (Synapse in
particular) can share them easier. Aside from the issues around
perception, I think it would make just as much sense to have them under
axis2/ (assuming we could release them separately, etc). No, I'm not
proposing that. :)
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Sanjiva
Sanjiva Weerawarana wrote:
> - First of all, Asankha, why "synapse-transports.jar"?? That makes no
> sense to me- so if you have a bug in the VFS code you'll rev all the
> stuff? Why? There should be one jar per transport. Yes, lots of jar
> files but so what?
>
> - Asankha, you seem to think that the only place transports that
> Synapse finds interesting are being done is in Synapse. What about
> CORBA? The code is in Axis2 (and Eranga is still waiting for his
> commit rights to come thru to finish that off) and of course
> supporting CORBA is very interesting for Synapse. So you're not
> solving whatever problem you perceive by saying "keep everything I
> care about in Synapse."
>
> - I agree with that Axis2 transports should NOT be in the kernel jar.
> Can we finally agree (forget the history please) to that now and
> create new maven modules for each transport and put each one into its
> own jar? This is for the transports that are (or will remain) in
> ws/axis2.
>
> - Given that these transports are usable by anyone building on Axis2
> (and not just Synapse) and that they depend on Axis2 APIs, I believe
> they should be in a project which releases those transports against
> given versions of Axis2 APIs. My preference is that it should be in
> ws/commons/transports or a new sub-project called ws/transports.
> Asankha, what problem do you see in that approach? I think everyone
> would +1 you being the RM for this project ;-).
+1 to all above
> - How about the following compromise position:
> - we create a new ws/transports project and move http and any other
> transports out of axis2 into that.
> - we kill the old NHTTP and JMS tranports in axis2
+1, lets get someone from Axis2 to do this as the first step. I will not
be able to work on this at least into the next few weeks..
> - move JMS and SMTP out of synapse into the new project
> - as a general rule, if Axis2 and Synapse are both going to ship the
> transport in their default distros, then we move the code here
> - for other transports we strongly encourage people to put them here
> to enable easier wider use
> - this project publishes each transport as a separate jar with a
> naming convention that identifies the axis2 (API) version it
> corresponds to. of course trunk will correspond to trunk as always
+1, Will move out the non Synapse specific transports into the new
module once the above project is created, and Axis2 moves out its http/s..
> - I'm ok with going one step further and even moving the Axis2
> transport APIs into the project and for Axis2 to just use them. This
> is like what Axis2 does with Axiom for example.
I maybe wrong.. but I don't see this as required or gives us additional
benefits..
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Sanjiva
Sanjiva Weerawarana wrote:
> - First of all, Asankha, why "synapse-transports.jar"?? That makes no
> sense to me- so if you have a bug in the VFS code you'll rev all the
> stuff? Why? There should be one jar per transport. Yes, lots of jar
> files but so what?
>
> - Asankha, you seem to think that the only place transports that
> Synapse finds interesting are being done is in Synapse. What about
> CORBA? The code is in Axis2 (and Eranga is still waiting for his
> commit rights to come thru to finish that off) and of course
> supporting CORBA is very interesting for Synapse. So you're not
> solving whatever problem you perceive by saying "keep everything I
> care about in Synapse."
>
> - I agree with that Axis2 transports should NOT be in the kernel jar.
> Can we finally agree (forget the history please) to that now and
> create new maven modules for each transport and put each one into its
> own jar? This is for the transports that are (or will remain) in
> ws/axis2.
>
> - Given that these transports are usable by anyone building on Axis2
> (and not just Synapse) and that they depend on Axis2 APIs, I believe
> they should be in a project which releases those transports against
> given versions of Axis2 APIs. My preference is that it should be in
> ws/commons/transports or a new sub-project called ws/transports.
> Asankha, what problem do you see in that approach? I think everyone
> would +1 you being the RM for this project ;-).
+1 to all above
> - How about the following compromise position:
> - we create a new ws/transports project and move http and any other
> transports out of axis2 into that.
> - we kill the old NHTTP and JMS tranports in axis2
+1, lets get someone from Axis2 to do this as the first step. I will not
be able to work on this at least into the next few weeks..
> - move JMS and SMTP out of synapse into the new project
> - as a general rule, if Axis2 and Synapse are both going to ship the
> transport in their default distros, then we move the code here
> - for other transports we strongly encourage people to put them here
> to enable easier wider use
> - this project publishes each transport as a separate jar with a
> naming convention that identifies the axis2 (API) version it
> corresponds to. of course trunk will correspond to trunk as always
+1, Will move out the non Synapse specific transports into the new
module once the above project is created, and Axis2 moves out its http/s..
> - I'm ok with going one step further and even moving the Axis2
> transport APIs into the project and for Axis2 to just use them. This
> is like what Axis2 does with Axiom for example.
I maybe wrong.. but I don't see this as required or gives us additional
benefits..
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Sanjaya Karunasena <sa...@wso2.com>.
Who will run all the transports in a single server? I like the ability to pick
and choose what I want. May be you will ship one or two key transports as
part of Axis2 and that is sufficient for most of the users.
This way if there is a bug in a particular transport that can be fixed and
released without affecting majority of the community.
/Sanjaya
On Wednesday 23 April 2008, Michele Mazzucco wrote:
> On 23 Apr 2008, at 18:20, Sanjiva Weerawarana wrote:
> > Michele Mazzucco wrote:
> >> Yes, since every jar file adds 1 to the number of files opened by
> >> a process (your JVM is a process itself). The default limit for
> >> files + socket that can be opened by a process is 1024.
> >
> > Um in toy systems maybe .. but this a tunable kernel parameter and
> > in any real server the number is much larger. This is hardly an
> > excuse for not properly modularizing code packaging. Plus the file
> > doesn't remain open- once the files are loaded in the FD is reused.
>
> This is a good reason indeed. You cannot ask somebody who would like
> to use axis2 to tune his/her kernel!
>
> Michele
>
> > Sanjiva.
> > --
> > Sanjiva Weerawarana, Ph.D.
> > Founder & Director; Lanka Software Foundation; http://
> > www.opensource.lk/
> > Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> > Member; Apache Software Foundation; http://www.apache.org/
> > Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
> >
> > ---------------------------------------------------------------------
> > 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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
On 23 Apr 2008, at 18:20, Sanjiva Weerawarana wrote:
> Michele Mazzucco wrote:
>> Yes, since every jar file adds 1 to the number of files opened by
>> a process (your JVM is a process itself). The default limit for
>> files + socket that can be opened by a process is 1024.
>
> Um in toy systems maybe .. but this a tunable kernel parameter and
> in any real server the number is much larger. This is hardly an
> excuse for not properly modularizing code packaging. Plus the file
> doesn't remain open- once the files are loaded in the FD is reused.
This is a good reason indeed. You cannot ask somebody who would like
to use axis2 to tune his/her kernel!
Michele
>
> Sanjiva.
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://
> www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Michele Mazzucco wrote:
>
> Yes, since every jar file adds 1 to the number of files opened by a
> process (your JVM is a process itself). The default limit for files +
> socket that can be opened by a process is 1024.
Um in toy systems maybe .. but this a tunable kernel parameter and in any
real server the number is much larger. This is hardly an excuse for not
properly modularizing code packaging. Plus the file doesn't remain open-
once the files are loaded in the FD is reused.
Sanjiva.
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
On 23 Apr 2008, at 14:24, Sanjiva Weerawarana wrote:
> Michele, its about making it easy to maintain and use. We gain
> nothing by putting them into the same jar file.
>
> With respect to your comment earlier saying
> "So you end up increasing the limits for files/sockets on you linux
> box"
> HUH?? What are you talking about?? This has nothing to do with
> limits for files or sockets!
Yes, since every jar file adds 1 to the number of files opened by a
process (your JVM is a process itself). The default limit for files +
socket that can be opened by a process is 1024.
Michele
>
> Sanjiva.
>
> Michele Mazzucco wrote:
>> Glen,
>> I disagree, each transport is composed by just a few classes, not
>> "megs of code".
>> I can't see really see where the problem is if you put JMS and
>> SMTP transports into the same jar file.
>> Michele
>> On 23 Apr 2008, at 13:09, Glen Daniels wrote:
>>> Hi Michele:
>>>
>>> Michele Mazzucco wrote:
>>>>> - First of all, Asankha, why "synapse-transports.jar"?? That
>>>>> makes no sense to me- so if you have a bug in the VFS code
>>>>> you'll rev all the stuff? Why? There should be one jar per
>>>>> transport.
>>>> Java provides packages for that. There's no need to have tons of
>>>> jars!
>>>
>>> There are well-understood tradeoffs between complication and
>>> flexibility here. Having one transport per jar means, as Sanjiva
>>> notes, that you can independently version and release
>>> transports. It also means that I don't need to carry around megs
>>> of code which is useless to me when I want just one transport.
>>>
>>> Forcing JMS and SMTP into one "transports.jar" seems just as
>>> weird to me as putting Axiom and Neethi into one "policy-and-
>>> xml.jar". :)
>>>
>>> Now, that said - I do think it's fine if you want to make a
>>> deployment *option* that's just one jar. I think Axis2 might
>>> also want to be making available an axis2-complete.jar (name not
>>> important) that has Axis2 plus all WS dependencies in it for ease
>>> of use in embedding scenarios. But I think these are convenience
>>> options that users can pick, as opposed to the right way to do
>>> things in the mainstream.
>>>
>>> Thanks,
>>> --Glen
>>>
>>> --------------------------------------------------------------------
>>> -
>>> 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
>
> --
> Sanjiva Weerawarana, Ph.D.
> Founder & Director; Lanka Software Foundation; http://
> www.opensource.lk/
> Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
> Member; Apache Software Foundation; http://www.apache.org/
> Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Michele, its about making it easy to maintain and use. We gain nothing by
putting them into the same jar file.
With respect to your comment earlier saying
"So you end up increasing the limits for files/sockets on you linux box"
HUH?? What are you talking about?? This has nothing to do with limits for
files or sockets!
Sanjiva.
Michele Mazzucco wrote:
> Glen,
>
> I disagree, each transport is composed by just a few classes, not "megs
> of code".
> I can't see really see where the problem is if you put JMS and SMTP
> transports into the same jar file.
>
> Michele
>
> On 23 Apr 2008, at 13:09, Glen Daniels wrote:
>
>> Hi Michele:
>>
>> Michele Mazzucco wrote:
>>>> - First of all, Asankha, why "synapse-transports.jar"?? That makes
>>>> no sense to me- so if you have a bug in the VFS code you'll rev all
>>>> the stuff? Why? There should be one jar per transport.
>>> Java provides packages for that. There's no need to have tons of jars!
>>
>> There are well-understood tradeoffs between complication and
>> flexibility here. Having one transport per jar means, as Sanjiva
>> notes, that you can independently version and release transports. It
>> also means that I don't need to carry around megs of code which is
>> useless to me when I want just one transport.
>>
>> Forcing JMS and SMTP into one "transports.jar" seems just as weird to
>> me as putting Axiom and Neethi into one "policy-and-xml.jar". :)
>>
>> Now, that said - I do think it's fine if you want to make a deployment
>> *option* that's just one jar. I think Axis2 might also want to be
>> making available an axis2-complete.jar (name not important) that has
>> Axis2 plus all WS dependencies in it for ease of use in embedding
>> scenarios. But I think these are convenience options that users can
>> pick, as opposed to the right way to do things in the mainstream.
>>
>> Thanks,
>> --Glen
>>
>> ---------------------------------------------------------------------
>> 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
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Glen,
I disagree, each transport is composed by just a few classes, not
"megs of code".
I can't see really see where the problem is if you put JMS and SMTP
transports into the same jar file.
Michele
On 23 Apr 2008, at 13:09, Glen Daniels wrote:
> Hi Michele:
>
> Michele Mazzucco wrote:
>>> - First of all, Asankha, why "synapse-transports.jar"?? That
>>> makes no sense to me- so if you have a bug in the VFS code you'll
>>> rev all the stuff? Why? There should be one jar per transport.
>> Java provides packages for that. There's no need to have tons of
>> jars!
>
> There are well-understood tradeoffs between complication and
> flexibility here. Having one transport per jar means, as Sanjiva
> notes, that you can independently version and release transports.
> It also means that I don't need to carry around megs of code which
> is useless to me when I want just one transport.
>
> Forcing JMS and SMTP into one "transports.jar" seems just as weird
> to me as putting Axiom and Neethi into one "policy-and-xml.jar". :)
>
> Now, that said - I do think it's fine if you want to make a
> deployment *option* that's just one jar. I think Axis2 might also
> want to be making available an axis2-complete.jar (name not
> important) that has Axis2 plus all WS dependencies in it for ease
> of use in embedding scenarios. But I think these are convenience
> options that users can pick, as opposed to the right way to do
> things in the mainstream.
>
> Thanks,
> --Glen
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Michele:
Michele Mazzucco wrote:
>> - First of all, Asankha, why "synapse-transports.jar"?? That makes no
>> sense to me- so if you have a bug in the VFS code you'll rev all the
>> stuff? Why? There should be one jar per transport.
>
> Java provides packages for that. There's no need to have tons of jars!
There are well-understood tradeoffs between complication and flexibility
here. Having one transport per jar means, as Sanjiva notes, that you
can independently version and release transports. It also means that I
don't need to carry around megs of code which is useless to me when I
want just one transport.
Forcing JMS and SMTP into one "transports.jar" seems just as weird to me
as putting Axiom and Neethi into one "policy-and-xml.jar". :)
Now, that said - I do think it's fine if you want to make a deployment
*option* that's just one jar. I think Axis2 might also want to be
making available an axis2-complete.jar (name not important) that has
Axis2 plus all WS dependencies in it for ease of use in embedding
scenarios. But I think these are convenience options that users can
pick, as opposed to the right way to do things in the mainstream.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
On 23 Apr 2008, at 05:11, Sanjiva Weerawarana wrote:
> - First of all, Asankha, why "synapse-transports.jar"?? That makes
> no sense to me- so if you have a bug in the VFS code you'll rev all
> the stuff? Why? There should be one jar per transport.
Java provides packages for that. There's no need to have tons of jars!
> Yes, lots of jar files but so what?
So you end up increasing the limits for files/sockets on you linux box
Michele
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hey Sanjiva:
Sanjiva Weerawarana wrote:
> - I agree with that Axis2 transports should NOT be in the kernel jar.
> Can we finally agree (forget the history please) to that now and create
> new maven modules for each transport and put each one into its own jar?
> This is for the transports that are (or will remain) in ws/axis2.
+1
And while we're at it (separate conversation though), perhaps transports
should be deployable as easily as services/modules...
conf/
modules/
services/
transports/
nhttp.tsp
jms.tsp
...with transport.xml inside *.tsp/META-INF
> - Given that these transports are usable by anyone building on Axis2
> (and not just Synapse) and that they depend on Axis2 APIs, I believe
> they should be in a project which releases those transports against
> given versions of Axis2 APIs. My preference is that it should be in
> ws/commons/transports or a new sub-project called ws/transports.
> Asankha, what problem do you see in that approach? I think everyone
> would +1 you being the RM for this project ;-).
Sounds like a plan. :)
See http://markmail.org/message/huukx25f3vgpethi - you might not have
seen that due to the lack of [axis2] prefix.
> - How about the following compromise position:
> - we create a new ws/transports project and move http and any other
> transports out of axis2 into that.
New mailing lists, then? (oh joy more folders :)) I could be ok with
this, but I think using commons is simpler.
> - we kill the old NHTTP and JMS tranports in axis2
Dims is already on this.
> - move JMS and SMTP out of synapse into the new project
+1. We should look at which if any of the Synapse transports are not
generally applicable outside the Synapse context, and move all the others.
> - as a general rule, if Axis2 and Synapse are both going to ship the
> transport in their default distros, then we move the code here
I'd tweak that - as a general rule, if the transport is generally useful
to both projects, it should live here to make sure it gets tested in
both contexts.
> - for other transports we strongly encourage people to put them here
> to enable easier wider use (e.g., WSO2 Mashup Server would inherit all
> the transports in Axis2 but not those from Synapse .. I think Asankha
> would want the new and improved SMTP transport to be in the WSO2 Mashup
> Server too ;-)). Of course we can't enforce that but I would hope that
> we should be able to come to a sufficient community understanding
> between the Synapse and WS TLPs to make that work.
+1
> - this project publishes each transport as a separate jar with a
> naming convention that identifies the axis2 (API) version it corresponds
> to. of course trunk will correspond to trunk as always
Need to think about that a bit.
> - I'm ok with going one step further and even moving the Axis2
> transport APIs into the project and for Axis2 to just use them. This is
> like what Axis2 does with Axiom for example.
+1, yup.
> The result is that the transports become an enabler for Axis2 (and
> Synapse and more) just as much as Axiom or XMLSchema is. The benefit is
> that they're no longer "Axis2's transports" or "Synapse's transports"
> but rather "those common transports". (I have to admit I didn't look at
> the code to evaluate the realisticness of this bit of the proposal - but
> the rest of it stands on its own anyway.)
Well, they ARE still Axis2 transports in that they exist to extend Axis2
- they're just in a common place so other users of Axis2 (Synapse in
particular) can share them easier. Aside from the issues around
perception, I think it would make just as much sense to have them under
axis2/ (assuming we could release them separately, etc). No, I'm not
proposing that. :)
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Wow, miss this list for a few days and boom!
Here's my attempt at a summary position:
- First of all, Asankha, why "synapse-transports.jar"?? That makes no
sense to me- so if you have a bug in the VFS code you'll rev all the
stuff? Why? There should be one jar per transport. Yes, lots of jar files
but so what?
- Asankha, you seem to think that the only place transports that Synapse
finds interesting are being done is in Synapse. What about CORBA? The code
is in Axis2 (and Eranga is still waiting for his commit rights to come
thru to finish that off) and of course supporting CORBA is very
interesting for Synapse. So you're not solving whatever problem you
perceive by saying "keep everything I care about in Synapse."
- I agree with that Axis2 transports should NOT be in the kernel jar. Can
we finally agree (forget the history please) to that now and create new
maven modules for each transport and put each one into its own jar? This
is for the transports that are (or will remain) in ws/axis2.
- Given that these transports are usable by anyone building on Axis2 (and
not just Synapse) and that they depend on Axis2 APIs, I believe they
should be in a project which releases those transports against given
versions of Axis2 APIs. My preference is that it should be in
ws/commons/transports or a new sub-project called ws/transports. Asankha,
what problem do you see in that approach? I think everyone would +1 you
being the RM for this project ;-).
- Asankha if you're going to stick a strong -1 in the middle of this
debate then I'm going to stick a strong -1 against the status quo of
Synapse maintaining its own transports. I think the rules now call for us
to keep talking ;-) ..
- How about the following compromise position:
- we create a new ws/transports project and move http and any other
transports out of axis2 into that.
- we kill the old NHTTP and JMS tranports in axis2
- move JMS and SMTP out of synapse into the new project
- as a general rule, if Axis2 and Synapse are both going to ship the
transport in their default distros, then we move the code here
- for other transports we strongly encourage people to put them here to
enable easier wider use (e.g., WSO2 Mashup Server would inherit all the
transports in Axis2 but not those from Synapse .. I think Asankha would
want the new and improved SMTP transport to be in the WSO2 Mashup Server
too ;-)). Of course we can't enforce that but I would hope that we should
be able to come to a sufficient community understanding between the
Synapse and WS TLPs to make that work.
- this project publishes each transport as a separate jar with a naming
convention that identifies the axis2 (API) version it corresponds to. of
course trunk will correspond to trunk as always
- I'm ok with going one step further and even moving the Axis2
transport APIs into the project and for Axis2 to just use them. This is
like what Axis2 does with Axiom for example.
The result is that the transports become an enabler for Axis2 (and Synapse
and more) just as much as Axiom or XMLSchema is. The benefit is that
they're no longer "Axis2's transports" or "Synapse's transports" but
rather "those common transports". (I have to admit I didn't look at the
code to evaluate the realisticness of this bit of the proposal - but the
rest of it stands on its own anyway.)
Sanjiva.
Asankha C. Perera wrote:
>
> Davanum Srinivas wrote:
>> Agreed that this is definitely a problem.
>>
>> Next question, is do you want do this in Synapse Commons (do you have
>> one?) or WS Commons?
> We already have all the transports in a separate Maven module, which is
> published to Apache snapshots and Central repo.. As far as I am concerned,
> there is no requirement to re-package this code and ship it elsewhere..
> If a user wants a particular transport as a separate module, they can
> ask for an enhancement for it, and we will do our best to facilitate it.
>
> So if we are going to have a vote on this 'topic' on axis-dev, I am +1
> to deleting the stale copies of the transports currently in Axis2.
>
> But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to make
> it easier for axis2 users to "get" these transports, I'm definitely -1
>
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Wow, miss this list for a few days and boom!
Here's my attempt at a summary position:
- First of all, Asankha, why "synapse-transports.jar"?? That makes no
sense to me- so if you have a bug in the VFS code you'll rev all the
stuff? Why? There should be one jar per transport. Yes, lots of jar files
but so what?
- Asankha, you seem to think that the only place transports that Synapse
finds interesting are being done is in Synapse. What about CORBA? The code
is in Axis2 (and Eranga is still waiting for his commit rights to come
thru to finish that off) and of course supporting CORBA is very
interesting for Synapse. So you're not solving whatever problem you
perceive by saying "keep everything I care about in Synapse."
- I agree with that Axis2 transports should NOT be in the kernel jar. Can
we finally agree (forget the history please) to that now and create new
maven modules for each transport and put each one into its own jar? This
is for the transports that are (or will remain) in ws/axis2.
- Given that these transports are usable by anyone building on Axis2 (and
not just Synapse) and that they depend on Axis2 APIs, I believe they
should be in a project which releases those transports against given
versions of Axis2 APIs. My preference is that it should be in
ws/commons/transports or a new sub-project called ws/transports. Asankha,
what problem do you see in that approach? I think everyone would +1 you
being the RM for this project ;-).
- Asankha if you're going to stick a strong -1 in the middle of this
debate then I'm going to stick a strong -1 against the status quo of
Synapse maintaining its own transports. I think the rules now call for us
to keep talking ;-) ..
- How about the following compromise position:
- we create a new ws/transports project and move http and any other
transports out of axis2 into that.
- we kill the old NHTTP and JMS tranports in axis2
- move JMS and SMTP out of synapse into the new project
- as a general rule, if Axis2 and Synapse are both going to ship the
transport in their default distros, then we move the code here
- for other transports we strongly encourage people to put them here to
enable easier wider use (e.g., WSO2 Mashup Server would inherit all the
transports in Axis2 but not those from Synapse .. I think Asankha would
want the new and improved SMTP transport to be in the WSO2 Mashup Server
too ;-)). Of course we can't enforce that but I would hope that we should
be able to come to a sufficient community understanding between the
Synapse and WS TLPs to make that work.
- this project publishes each transport as a separate jar with a naming
convention that identifies the axis2 (API) version it corresponds to. of
course trunk will correspond to trunk as always
- I'm ok with going one step further and even moving the Axis2
transport APIs into the project and for Axis2 to just use them. This is
like what Axis2 does with Axiom for example.
The result is that the transports become an enabler for Axis2 (and Synapse
and more) just as much as Axiom or XMLSchema is. The benefit is that
they're no longer "Axis2's transports" or "Synapse's transports" but
rather "those common transports". (I have to admit I didn't look at the
code to evaluate the realisticness of this bit of the proposal - but the
rest of it stands on its own anyway.)
Sanjiva.
Asankha C. Perera wrote:
>
> Davanum Srinivas wrote:
>> Agreed that this is definitely a problem.
>>
>> Next question, is do you want do this in Synapse Commons (do you have
>> one?) or WS Commons?
> We already have all the transports in a separate Maven module, which is
> published to Apache snapshots and Central repo.. As far as I am concerned,
> there is no requirement to re-package this code and ship it elsewhere..
> If a user wants a particular transport as a separate module, they can
> ask for an enhancement for it, and we will do our best to facilitate it.
>
> So if we are going to have a vote on this 'topic' on axis-dev, I am +1
> to deleting the stale copies of the transports currently in Axis2.
>
> But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to make
> it easier for axis2 users to "get" these transports, I'm definitely -1
>
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Andreas Veithen <an...@skynet.be>.
I would propose to leave the transports in Synapse but to have a
distinct Maven module for each protocol, with the minimal set of
dependencies required for that protocol implementation. This would
allow Axis2 users to include these transport easily in their Maven
builds. It would also be interesting to Synapse users: As an example,
I have a project where I package Synapse together with the relevant
config files into a WAR. With Synapse 1.1.1, the WAR takes 24MB, with
the latest snapshots, 32MB. The dependencies for the FIX protocol
(which I will never use) alone take more than 4MB. Having different
Maven modules for the various transports would allow better control of
what is included in the packaging.
Andreas
On 22 Apr 2008, at 22:41, Asankha C. Perera wrote:
>
> Davanum Srinivas wrote:
>> Agreed that this is definitely a problem.
>>
>> Next question, is do you want do this in Synapse Commons (do you
>> have one?) or WS Commons?
> We already have all the transports in a separate Maven module, which
> is published to Apache snapshots and Central repo.. As far as I am
> concerned,
> there is no requirement to re-package this code and ship it
> elsewhere.. If a user wants a particular transport as a separate
> module, they can ask for an enhancement for it, and we will do our
> best to facilitate it.
>
> So if we are going to have a vote on this 'topic' on axis-dev, I am
> +1 to deleting the stale copies of the transports currently in Axis2.
>
> But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to
> make it easier for axis2 users to "get" these transports, I'm
> definitely -1
>
> asankha
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cool. I'll cleanup whatever stale transports are in Axis2.
thanks,
dims
Asankha C. Perera wrote:
|
| Davanum Srinivas wrote:
|> Agreed that this is definitely a problem.
|>
|> Next question, is do you want do this in Synapse Commons (do you have
|> one?) or WS Commons?
| We already have all the transports in a separate Maven module, which is
| published to Apache snapshots and Central repo.. As far as I am concerned,
| there is no requirement to re-package this code and ship it elsewhere..
| If a user wants a particular transport as a separate module, they can
| ask for an enhancement for it, and we will do our best to facilitate it.
|
| So if we are going to have a vote on this 'topic' on axis-dev, I am +1
| to deleting the stale copies of the transports currently in Axis2.
|
| But if you are going to call for a vote on dev@synapse.a.o to remove
| critical code developed by the Synapse community from our SVN, to make
| it easier for axis2 users to "get" these transports, I'm definitely -1
|
| asankha
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| For additional commands, e-mail: axis-dev-help@ws.apache.org
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDk7tgNg6eWEDv1kRAlBMAKDMM3929V3s4wq4w450rjg3tpkgBACg+X2A
56bw+SVyNqndLOgSAGszrUg=
=oKu/
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hey Asankha:
Just wanted to quickly reply to this.
Asankha C. Perera wrote:
> So if we are going to have a vote on this 'topic' on axis-dev, I am +1
> to deleting the stale copies of the transports currently in Axis2.
+1, for sure.
> But if you are going to call for a vote on dev@synapse.a.o to remove
> critical code developed by the Synapse community from our SVN, to make
> it easier for axis2 users to "get" these transports, I'm definitely -1
I'm "not" exactly sure what the "quotes" mean here :), but I think you
might be looking at this the wrong way. It's not that anyone wants to
wrest control of your code from you - it's that we want to put things
where they make sense. Axiom (or Neethi) is just as critical to Synapse
as any of these transports, and that's in WS-Commons - do you want that
in Synapse too? You, Asankha, as a WS-Commons committer, have exactly
as much control over the code there as you do the code in Synapse, and
of course the devs that have done the work on these up until now will
continue to work on them wherever they live.
Are you not actually interested in making it easy for Axis2 users to
obtain and use these transports?
Anyway, I think I've made my points in the other mails already; I hope
you'll step back a bit and consider. Honestly, as long as there's a
separate transports area with individual transports releasable on their
own, I don't *really* care all that much where it is - but it does seem
to me that it makes more sense in commons than it does in Synapse, for
all the transports that are usable in both contexts.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Cool. I'll cleanup whatever stale transports are in Axis2.
thanks,
dims
Asankha C. Perera wrote:
|
| Davanum Srinivas wrote:
|> Agreed that this is definitely a problem.
|>
|> Next question, is do you want do this in Synapse Commons (do you have
|> one?) or WS Commons?
| We already have all the transports in a separate Maven module, which is
| published to Apache snapshots and Central repo.. As far as I am concerned,
| there is no requirement to re-package this code and ship it elsewhere..
| If a user wants a particular transport as a separate module, they can
| ask for an enhancement for it, and we will do our best to facilitate it.
|
| So if we are going to have a vote on this 'topic' on axis-dev, I am +1
| to deleting the stale copies of the transports currently in Axis2.
|
| But if you are going to call for a vote on dev@synapse.a.o to remove
| critical code developed by the Synapse community from our SVN, to make
| it easier for axis2 users to "get" these transports, I'm definitely -1
|
| asankha
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| For additional commands, e-mail: axis-dev-help@ws.apache.org
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDk7tgNg6eWEDv1kRAlBMAKDMM3929V3s4wq4w450rjg3tpkgBACg+X2A
56bw+SVyNqndLOgSAGszrUg=
=oKu/
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Davanum Srinivas wrote:
> Agreed that this is definitely a problem.
>
> Next question, is do you want do this in Synapse Commons (do you have
> one?) or WS Commons?
We already have all the transports in a separate Maven module, which is
published to Apache snapshots and Central repo.. As far as I am concerned,
there is no requirement to re-package this code and ship it elsewhere..
If a user wants a particular transport as a separate module, they can
ask for an enhancement for it, and we will do our best to facilitate it.
So if we are going to have a vote on this 'topic' on axis-dev, I am +1
to deleting the stale copies of the transports currently in Axis2.
But if you are going to call for a vote on dev@synapse.a.o to remove
critical code developed by the Synapse community from our SVN, to make
it easier for axis2 users to "get" these transports, I'm definitely -1
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Davanum Srinivas wrote:
> Agreed that this is definitely a problem.
>
> Next question, is do you want do this in Synapse Commons (do you have
> one?) or WS Commons?
We already have all the transports in a separate Maven module, which is
published to Apache snapshots and Central repo.. As far as I am concerned,
there is no requirement to re-package this code and ship it elsewhere..
If a user wants a particular transport as a separate module, they can
ask for an enhancement for it, and we will do our best to facilitate it.
So if we are going to have a vote on this 'topic' on axis-dev, I am +1
to deleting the stale copies of the transports currently in Axis2.
But if you are going to call for a vote on dev@synapse.a.o to remove
critical code developed by the Synapse community from our SVN, to make
it easier for axis2 users to "get" these transports, I'm definitely -1
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Agreed that this is definitely a problem.
Next question, is do you want do this in Synapse Commons (do you have one?) or WS Commons?
- -- dims
Ruwan Linton wrote:
| Dims,
|
| I agree there is no -1, but at the same time we couldn't get those fixes
| into axis2 SMTP transport on our release time frame of synapse and we went
| ahead with our own one.
|
| BTW: If we are to move these transports out from synapse, it has to be in to
| a separate commons project (not on to axis2), so that we have the control
| over them to do the required changes.
|
| Thanks,
| Ruwan
|
| On Wed, Apr 23, 2008 at 1:17 AM, Davanum Srinivas <da...@gmail.com> wrote:
|
| Ruwan,
|
| All i see is some discussion, which happens on a topic
|
| http://marc.info/?t=119684680300006&r=1&w=3
|
| - Where is the push back? From who?
| - Where is the VOTE?
| - Where is a -1?
|
| thanks,
| dims
|
| Ruwan Linton wrote:
| | Dims,
| |
| | I couldn't find this on the axis2 mail archives, that thread was having
| the
| | subject "Improvement to mail transport from a Synapse use case" and
| posted
| | by saminda to the axis-dev.
| |
| | Here is the relevant thread on Synapse [
| | http://mail-archives.apache.org/mod_mbox/synapse-user/200712.mbox/thread
| ]
| |
| | Thanks,
| | Ruwan
| |
| | On Wed, Apr 23, 2008 at 12:16 AM, Davanum Srinivas <da...@gmail.com>
| | wrote:
| | Ruwan,
| |
| | How about a pointer to a public discussion on why SMTP Transport changes
| |> were debated? :)
| | -- dims
| |
| |
| |
| |
| | Ruwan Linton wrote:
| | | Glen,
| | |
| | | I agree with you. But my concern is the history. That is, when ever we
| | | (synapse) wanted some transport specific feature for synapse to be
| added
| |> to
| | | axis2 transports axis2 community was not accepting them due to many
| |> reasons
| | | most of them are valid for web services, but from the synapse point of
| |> view,
| | | we do not need to (and should not) bound to the web services. Isn't
| it?
| | |
| | | This behavior is affecting the evolution of synapse and that is why we
| |> went
| | | ahead and developed our own transports. (Best example is the SMTP
| |> transport)
| | |
| | | Thanks,
| | | Ruwan
| | |
| | | On Tue, Apr 22, 2008 at 11:48 PM, Glen Daniels <gl...@thoughtcraft.com>
| | | wrote:
| | |
| | |> Hi Ruwan:
| | |>
| | |> If a given transport really only has relevance in the Synapse
| |> environment,
| | |> then of course that transport has no need to exist outside Synapse.
| |> But if
| | |> a transport is generically useful, I'd prefer to see it somewhere in
| WS
| | |> space as opposed to specifically within Synapse. And if some generic
| | |> transport needs tweaking in particular ways for Synapse, then those
| |> ways
| | |> should be exposed as configuration or plug-points on the transport,
| |> which
| | |> get exercised by Synapse (but also tested in the transport build).
| |> Example
| | |> - the nhttp transport could just include a callback property which,
| if
| |> set,
| | |> passes the 202 to a listener and ignores it otherwise (perhaps that's
| | |> exactly the way it works). In the SMTP case, we should discuss what
| | |> happens, but again I don't see any issue with making a clean and
| useful
| | |> general SMTP transport - why should there need to be two of them??
| | |>
| | |> Here's my use case. Someone wants to use nhttp, or JMS, or SMTP,
| with
| | |> Axis2. They're not a Synapse user and are not interested in
| |> downloading
| | |> Synapse. I want to make sure that this user can easily locate,
| |> download,
| | |> and install the transport they want. At the same time I want the
| Axis2
| |> and
| | |> the Synapse communities both sharing their skills to make the best
| set
| |> of
| | |> transports available for Axis2 and of course Axis2+Synapse.
| | |>
| | |> I'm not wedded to the details, as long as we can make that happen.
| It
| | |> seems to me right now that ws-commons/transports is a better way to
| do
| |> this
| | |> than having lots of extension transports in Synapse, but I'm willing
| to
| |> be
| | |> convinced otherwise.
| | |>
| | |> Thanks,
| | |> --Glen
| | |>
| | |> Ruwan Linton wrote:
| | |>
| | |>> I forgot to mention that, of cause one can use these transports with
| | |>> knowing the limitations and issues of those, when working directly
| |> with
| | |>> axis2
| | |>>
| | |>> Thanks,
| | |>> Ruwan
| | |>>
| | |>> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <
| ruwan.linton@gmail.com
| |> <mailto:
| | |>> ruwan.linton@gmail.com>> wrote:
| | |>>
| | |>> Hi Dims, Glen and all,
| | |>>
| | |>> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
| | |>> <davanum@gmail.com <ma...@gmail.com>> wrote:
| | |>>
| |
| |
| |
| | | Glen,
| | |
| | | At this point, Can we please agree that it's better for the
| | | people who actually work on it have their way :)
| | |
| | |
| | |>>> +1 for this idea ... and one more thing is that;
| | |
| | |>>> Although the transports which resides under synapse code base
| are
| | |>>> just axis2 transports, there are some special cases that synapse
| | |>>> needs from its transports. For example;
| | |
| | | * nhttp transport requires 202 Accepted HTTP messages to be
| | | injected inside to synapse so that it can complete mediation
| | | of one-way messages as well as we need those messages to be
| | | injected on the separateListener case, where as axis2 should
| | | just neglect those HTTP messages.
| | | * Same with 500 Internal Server Error on nhttp
| | | * smtp transport requires to treat all the Cc headers and Cc the
| | | message to all the specified addresses (we have discussed this
| | | earlier on axis2 and this is wrong according to the WS-MEPs,
| | | because there are many outs)
| | |
| | |>>> There are a number of synapse specific logic inside synapse
| | |>>> transports, because synapse is not purely bound to WS space, but
| |> it
| | |>>> is a mediation framework (ESB) which should support most of the
| | |>>> other scenarios going out of the WS space. There for these
| | |>>> transports may not directly work with axis2 and it is not at all
| a
| | |>>> good idea to move them out from synapse code base.
| | |
| | |>>> Thanks,
| | |>>> Ruwan
| | |
| | |
| | |
| | | thanks,
| | | dims
| | |
| | |
| | | Glen Daniels wrote:
| | | | Asankha C. Perera wrote:
| | | |> Dims
| | | |>> - there should not be stale copies
| | | |>> - people who work on them should work where they want to.
| | | |> +1 to both!
| | | |
| | | | Agreed - I'd just prefer people wanted to work on them under
| | | WS/Axis. :)
| | | |
| | | |> I'd like to maintain these under Synapse.. We wrote these
| | | transports
| | | |> primarily for use by Synapse, and now we have JMS,
| | | NIO-HTTP/S, Mail,
| | | |> VFS (File), FIX and AMQP already.. These belong to a separate
| | | Maven
| | | |> module thats published to the Apache snapshots and Maven
| | |>>> Central
| | | |> repos, and
| | | |
| | | | Hm. So this is a bit of a separate conversation, but *each*
| | | of the
| | | | transports should be its own deployable artifact. If I want
| | | the AMQP
| | | | transport for some work I'm doing, I don't want to bother
| | | downloading
| | | | all the others.... Wherever they end up we should fix that!!
| | | |
| | | |> this JAR does not depend on the Synapse codebase at all.
| | | Anyone who
| | | |> wishes to use these can do so without any problems
| | | whatsoever, and
| | | |> raise JIRA's for bugs/enhancements where the code is actually
| | | maintained.
| | | |
| | | | Yeah. I just think this makes a lot more sense under WS.
| | | |
| | | |>> | | These transports (JMS, NIO, whatever) are going to be
| | | generally
| | | |>> useful to any Axis2 user, so why make them go look in
| | |>>> Synapse's
| | | |>> codebase for them?
| | | |> I agree,.. however these transports were written by the
| | |>>> Synapse
| | | |> community for primary use by them. So instead of asking them
| | |>>> to
| | | |> maintain the code they write somewhere else - for the
| | | convenience of
| | | |> the secondary users, why not clearly document the available
| | | options
| | | |> under Axis2 and where one could download these extension
| | | transports
| | | |> developed by the Synapse community?
| | | |
| | | | Sure, I'm not saying that wouldn't work - what's really
| | | important to me
| | | | is that Axis2 users get a clear picture of the available
| | | transports when
| | | | they download Axis2 and use our website. This is both to avoid
| | | | duplication of effort and to enable users to use the richest
| | | set of
| | | | components available. It seems to me that the most natural way
| | |>>> to
| | | | achieve this is to contribute new transports to ws-commons or
| | | Axis2.
| | | |
| | | | Also consider this - wouldn't it be cool to be able to run the
| | | Axis2
| | | | test suite (which is presumably much more comprehensive than
| | | Synapse's
| | | | testing of Axis2) over each of the transports that Synapse
| | | originally
| | | | built? I would think that might demonstrate some issues that
| | | Synapse
| | | | itself might not find, thus enabling the transports to be
| | | improved.
| | | |
| | | | But if the community wants to keep developing these under
| | | Synapse, then
| | | | we definitely need some pointers in the Axis2 code and web
| | | pages, and
| | | | those pointers need to be maintained.
| | | |
| | | | Thanks,
| | | | --Glen
| | | |
| | | |
| | |
| | |>>>
| |> ---------------------------------------------------------------------
| | | | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| | | <ma...@ws.apache.org>
| | | | For additional commands, e-mail: axis-dev-help@ws.apache.org
| | | <ma...@ws.apache.org>
| | | |
| | |>>
| | |>>
| | |>>
| |
| | |>>
| ---------------------------------------------------------------------
| | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| | <ma...@ws.apache.org>
| | For additional commands, e-mail: axis-dev-help@ws.apache.org
| | <ma...@ws.apache.org>
| | |>>
| | |>>
| | |>>
| | |>>
| | |>> -- Ruwan Linton
| | |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
| | |>>
| | |>>
| | |>>
| | |>> --
| | |>> Ruwan Linton
| | |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
| | |>>
| | |> ---------------------------------------------------------------------
| | |> 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
| |>
| |>
|
|>
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
|>
|>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDkjrgNg6eWEDv1kRAuGrAJ9i68sD0DZ0tNQcRIPNF5vM9XSyYACePxMC
mx0ZcjXfZ8XARq6IuL7XRmM=
=+UFi
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
Dims,
I agree there is no -1, but at the same time we couldn't get those fixes
into axis2 SMTP transport on our release time frame of synapse and we went
ahead with our own one.
BTW: If we are to move these transports out from synapse, it has to be in to
a separate commons project (not on to axis2), so that we have the control
over them to do the required changes.
Thanks,
Ruwan
On Wed, Apr 23, 2008 at 1:17 AM, Davanum Srinivas <da...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ruwan,
>
> All i see is some discussion, which happens on a topic
>
> http://marc.info/?t=119684680300006&r=1&w=3
>
> - - Where is the push back? From who?
> - - Where is the VOTE?
> - - Where is a -1?
>
> thanks,
> dims
>
> Ruwan Linton wrote:
> | Dims,
> |
> | I couldn't find this on the axis2 mail archives, that thread was having
> the
> | subject "Improvement to mail transport from a Synapse use case" and
> posted
> | by saminda to the axis-dev.
> |
> | Here is the relevant thread on Synapse [
> | http://mail-archives.apache.org/mod_mbox/synapse-user/200712.mbox/thread
> ]
> |
> | Thanks,
> | Ruwan
> |
> | On Wed, Apr 23, 2008 at 12:16 AM, Davanum Srinivas <da...@gmail.com>
> | wrote:
> | Ruwan,
> |
> | How about a pointer to a public discussion on why SMTP Transport changes
> |> were debated? :)
> | -- dims
> |
> |
> |
> |
> | Ruwan Linton wrote:
> | | Glen,
> | |
> | | I agree with you. But my concern is the history. That is, when ever we
> | | (synapse) wanted some transport specific feature for synapse to be
> added
> |> to
> | | axis2 transports axis2 community was not accepting them due to many
> |> reasons
> | | most of them are valid for web services, but from the synapse point of
> |> view,
> | | we do not need to (and should not) bound to the web services. Isn't
> it?
> | |
> | | This behavior is affecting the evolution of synapse and that is why we
> |> went
> | | ahead and developed our own transports. (Best example is the SMTP
> |> transport)
> | |
> | | Thanks,
> | | Ruwan
> | |
> | | On Tue, Apr 22, 2008 at 11:48 PM, Glen Daniels <gl...@thoughtcraft.com>
> | | wrote:
> | |
> | |> Hi Ruwan:
> | |>
> | |> If a given transport really only has relevance in the Synapse
> |> environment,
> | |> then of course that transport has no need to exist outside Synapse.
> |> But if
> | |> a transport is generically useful, I'd prefer to see it somewhere in
> WS
> | |> space as opposed to specifically within Synapse. And if some generic
> | |> transport needs tweaking in particular ways for Synapse, then those
> |> ways
> | |> should be exposed as configuration or plug-points on the transport,
> |> which
> | |> get exercised by Synapse (but also tested in the transport build).
> |> Example
> | |> - the nhttp transport could just include a callback property which,
> if
> |> set,
> | |> passes the 202 to a listener and ignores it otherwise (perhaps that's
> | |> exactly the way it works). In the SMTP case, we should discuss what
> | |> happens, but again I don't see any issue with making a clean and
> useful
> | |> general SMTP transport - why should there need to be two of them??
> | |>
> | |> Here's my use case. Someone wants to use nhttp, or JMS, or SMTP,
> with
> | |> Axis2. They're not a Synapse user and are not interested in
> |> downloading
> | |> Synapse. I want to make sure that this user can easily locate,
> |> download,
> | |> and install the transport they want. At the same time I want the
> Axis2
> |> and
> | |> the Synapse communities both sharing their skills to make the best
> set
> |> of
> | |> transports available for Axis2 and of course Axis2+Synapse.
> | |>
> | |> I'm not wedded to the details, as long as we can make that happen.
> It
> | |> seems to me right now that ws-commons/transports is a better way to
> do
> |> this
> | |> than having lots of extension transports in Synapse, but I'm willing
> to
> |> be
> | |> convinced otherwise.
> | |>
> | |> Thanks,
> | |> --Glen
> | |>
> | |> Ruwan Linton wrote:
> | |>
> | |>> I forgot to mention that, of cause one can use these transports with
> | |>> knowing the limitations and issues of those, when working directly
> |> with
> | |>> axis2
> | |>>
> | |>> Thanks,
> | |>> Ruwan
> | |>>
> | |>> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <
> ruwan.linton@gmail.com
> |> <mailto:
> | |>> ruwan.linton@gmail.com>> wrote:
> | |>>
> | |>> Hi Dims, Glen and all,
> | |>>
> | |>> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
> | |>> <davanum@gmail.com <ma...@gmail.com>> wrote:
> | |>>
> |
> |
> |
> | | Glen,
> | |
> | | At this point, Can we please agree that it's better for the
> | | people who actually work on it have their way :)
> | |
> | |
> | |>>> +1 for this idea ... and one more thing is that;
> | |
> | |>>> Although the transports which resides under synapse code base
> are
> | |>>> just axis2 transports, there are some special cases that synapse
> | |>>> needs from its transports. For example;
> | |
> | | * nhttp transport requires 202 Accepted HTTP messages to be
> | | injected inside to synapse so that it can complete mediation
> | | of one-way messages as well as we need those messages to be
> | | injected on the separateListener case, where as axis2 should
> | | just neglect those HTTP messages.
> | | * Same with 500 Internal Server Error on nhttp
> | | * smtp transport requires to treat all the Cc headers and Cc the
> | | message to all the specified addresses (we have discussed this
> | | earlier on axis2 and this is wrong according to the WS-MEPs,
> | | because there are many outs)
> | |
> | |>>> There are a number of synapse specific logic inside synapse
> | |>>> transports, because synapse is not purely bound to WS space, but
> |> it
> | |>>> is a mediation framework (ESB) which should support most of the
> | |>>> other scenarios going out of the WS space. There for these
> | |>>> transports may not directly work with axis2 and it is not at all
> a
> | |>>> good idea to move them out from synapse code base.
> | |
> | |>>> Thanks,
> | |>>> Ruwan
> | |
> | |
> | |
> | | thanks,
> | | dims
> | |
> | |
> | | Glen Daniels wrote:
> | | | Asankha C. Perera wrote:
> | | |> Dims
> | | |>> - there should not be stale copies
> | | |>> - people who work on them should work where they want to.
> | | |> +1 to both!
> | | |
> | | | Agreed - I'd just prefer people wanted to work on them under
> | | WS/Axis. :)
> | | |
> | | |> I'd like to maintain these under Synapse.. We wrote these
> | | transports
> | | |> primarily for use by Synapse, and now we have JMS,
> | | NIO-HTTP/S, Mail,
> | | |> VFS (File), FIX and AMQP already.. These belong to a separate
> | | Maven
> | | |> module thats published to the Apache snapshots and Maven
> | |>>> Central
> | | |> repos, and
> | | |
> | | | Hm. So this is a bit of a separate conversation, but *each*
> | | of the
> | | | transports should be its own deployable artifact. If I want
> | | the AMQP
> | | | transport for some work I'm doing, I don't want to bother
> | | downloading
> | | | all the others.... Wherever they end up we should fix that!!
> | | |
> | | |> this JAR does not depend on the Synapse codebase at all.
> | | Anyone who
> | | |> wishes to use these can do so without any problems
> | | whatsoever, and
> | | |> raise JIRA's for bugs/enhancements where the code is actually
> | | maintained.
> | | |
> | | | Yeah. I just think this makes a lot more sense under WS.
> | | |
> | | |>> | | These transports (JMS, NIO, whatever) are going to be
> | | generally
> | | |>> useful to any Axis2 user, so why make them go look in
> | |>>> Synapse's
> | | |>> codebase for them?
> | | |> I agree,.. however these transports were written by the
> | |>>> Synapse
> | | |> community for primary use by them. So instead of asking them
> | |>>> to
> | | |> maintain the code they write somewhere else - for the
> | | convenience of
> | | |> the secondary users, why not clearly document the available
> | | options
> | | |> under Axis2 and where one could download these extension
> | | transports
> | | |> developed by the Synapse community?
> | | |
> | | | Sure, I'm not saying that wouldn't work - what's really
> | | important to me
> | | | is that Axis2 users get a clear picture of the available
> | | transports when
> | | | they download Axis2 and use our website. This is both to avoid
> | | | duplication of effort and to enable users to use the richest
> | | set of
> | | | components available. It seems to me that the most natural way
> | |>>> to
> | | | achieve this is to contribute new transports to ws-commons or
> | | Axis2.
> | | |
> | | | Also consider this - wouldn't it be cool to be able to run the
> | | Axis2
> | | | test suite (which is presumably much more comprehensive than
> | | Synapse's
> | | | testing of Axis2) over each of the transports that Synapse
> | | originally
> | | | built? I would think that might demonstrate some issues that
> | | Synapse
> | | | itself might not find, thus enabling the transports to be
> | | improved.
> | | |
> | | | But if the community wants to keep developing these under
> | | Synapse, then
> | | | we definitely need some pointers in the Axis2 code and web
> | | pages, and
> | | | those pointers need to be maintained.
> | | |
> | | | Thanks,
> | | | --Glen
> | | |
> | | |
> | |
> | |>>>
> |> ---------------------------------------------------------------------
> | | | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> | | <ma...@ws.apache.org>
> | | | For additional commands, e-mail: axis-dev-help@ws.apache.org
> | | <ma...@ws.apache.org>
> | | |
> | |>>
> | |>>
> | |>>
> |
> | |>>
> ---------------------------------------------------------------------
> | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> | <ma...@ws.apache.org>
> | For additional commands, e-mail: axis-dev-help@ws.apache.org
> | <ma...@ws.apache.org>
> | |>>
> | |>>
> | |>>
> | |>>
> | |>> -- Ruwan Linton
> | |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
> | |>>
> | |>>
> | |>>
> | |>> --
> | |>> Ruwan Linton
> | |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
> | |>>
> | |> ---------------------------------------------------------------------
> | |> 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
> |>
> |>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD4DBQFIDkDSgNg6eWEDv1kRAgbhAJ4hEqtqTp7Xc2C2SoKRp7x85H8lHQCY144n
> UEgjToYwR6teYulTJdfFIA==
> =lhqw
>
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ruwan,
I was not around, i can't speak for others. I did not participate in that thread. Let's treat it as water under the bridge.
I'll go ahead and get rid of stale code in Axis2 and let's be done with it. Synapse committers can do what they think
best. I will close all the related JIRA items as well as wont-fix.
thanks,
dims
Ruwan Linton wrote:
| Dims,
|
| If the axis2 community had agreed to do that then one of the core members of
| the axis2 team should do that, (we don't want to move the code inside axis2
| and mess with your project, would you like me moving the transports out from
| axis2 kernel??? also with the objections in that thread), but as you can
| clearly see there were tons of objections and no one was ready to move them
| out except for Deepal and Sanjiva? Again I agree there was no vote, but that
| did not happen....
|
| Thanks,
| Ruwan
|
| On Wed, Apr 23, 2008 at 2:24 AM, Davanum Srinivas <da...@gmail.com> wrote:
|
| Asankha,
|
| FWIW,
|
| 1) I see a +1 from Deepal and Dr. Sanjiva
| 2) No one did a -1
| 3) There was no VOTE
|
| So, where's the beef? AFAICT, No one objected to someone else doing the
| work :)
|
| So all i can see is an implicit and not to mention unilateral decision to
| fork the code and leave the copy in Axis2 stale.
|
| -- dims
|
| Asankha C. Perera wrote:
| | Check this thread
| |
| <
|
http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/%3c672a01200710022224t1e100d77gb83e7bcfeeb8ad94@mail.gmail.com%3e
|
| | as well titled "Getting axis2 transport out from the kernel"
| |
| | asankha
| |
| | Davanum Srinivas wrote:
| |> Ruwan,
| |>
| |> All i see is some discussion, which happens on a topic
| |>
| |> http://marc.info/?t=119684680300006&r=1&w=3
| |>
| |> - Where is the push back? From who?
| |> - Where is the VOTE?
| |> - Where is a -1?
| |>
| |> thanks,
| |> dims
| |
| |
|>
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
|>
|>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDlTLgNg6eWEDv1kRAm3XAJ0clhpFE1S1QLp1MrtCQxn62PpMcQCfdyCk
L7p0EV6pDt3zy5FYoPeQZtM=
=aCzB
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Ruwan, no one is going to (or even ABLE to, for that matter) force the
Synapse team to do anything. We're trying to work together here, and
build a system of interacting parts that work well together for the
largest possible number of satisfied users (sounds like some companies I
know :)). I'm a commiter on both projects, and I'm trying to convince
you that this might be a good move for everyone.
Synapse *is* building Axis2 transports - that's the long and the short
of it. It's fine if Synapse wants to keep those transports under
Synapse, and it's fine if we move them into commons Transports, the
world won't end either way.
Personally, I think it's vastly preferable to work on these together as
Axis2/WS components, and try to make them as generally useful as
possible. If there are particular ones that are truly Synapse specific
then by all means, keep them in Synapse. But please note that if the
generally useful ones are in Synapse, that means that if there's a
problem using one of them in a non-Synapse Axis2 situation, the Axis2
team would have exactly the same issues trying to get the Synapse team
to fix it.... Wouldn't it be better to have one place where both teams
can work on them?
Re: the earlier mail, I wasn't involved in that earlier thread but I
have always been +1 to getting the transports in Axis2 into a separate
module, because it's important that they be pluggable components.
Thanks,
--Glen
Ruwan Linton wrote:
> Dims,
>
> If the axis2 community had agreed to do that then one of the core
> members of the axis2 team should do that, (we don't want to move the
> code inside axis2 and mess with your project, would you like me moving
> the transports out from axis2 kernel??? also with the objections in that
> thread), but as you can clearly see there were tons of objections and no
> one was ready to move them out except for Deepal and Sanjiva? Again I
> agree there was no vote, but that did not happen....
>
> Thanks,
> Ruwan
>
> On Wed, Apr 23, 2008 at 2:24 AM, Davanum Srinivas <davanum@gmail.com
> <ma...@gmail.com>> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Asankha,
>
> FWIW,
>
> 1) I see a +1 from Deepal and Dr. Sanjiva
> 2) No one did a -1
> 3) There was no VOTE
>
> So, where's the beef? AFAICT, No one objected to someone else doing
> the work :)
>
> So all i can see is an implicit and not to mention unilateral
> decision to fork the code and leave the copy in Axis2 stale.
>
> - -- dims
>
> Asankha C. Perera wrote:
> | Check this thread
> |
> <http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/%3c672a01200710022224t1e100d77gb83e7bcfeeb8ad94@mail.gmail.com%3e>
>
>
> | as well titled "Getting axis2 transport out from the kernel"
> |
> | asankha
> |
> | Davanum Srinivas wrote:
> |> Ruwan,
> |>
> |> All i see is some discussion, which happens on a topic
> |>
> |> http://marc.info/?t=119684680300006&r=1&w=3
> <http://marc.info/?t=119684680300006&r=1&w=3>
> |>
> |> - Where is the push back? From who?
> |> - Where is the VOTE?
> |> - Where is a -1?
> |>
> |> thanks,
> |> dims
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDlCRgNg6eWEDv1kRAuSDAKCtn+NYtfbFSiR/qXd4wncGymFhywCeNBjU
> 86McoG01Pp5nJ2ahQFYJrk0=
> =kPhE
>
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ruwan,
I was not around, i can't speak for others. I did not participate in that thread. Let's treat it as water under the bridge.
I'll go ahead and get rid of stale code in Axis2 and let's be done with it. Synapse committers can do what they think
best. I will close all the related JIRA items as well as wont-fix.
thanks,
dims
Ruwan Linton wrote:
| Dims,
|
| If the axis2 community had agreed to do that then one of the core members of
| the axis2 team should do that, (we don't want to move the code inside axis2
| and mess with your project, would you like me moving the transports out from
| axis2 kernel??? also with the objections in that thread), but as you can
| clearly see there were tons of objections and no one was ready to move them
| out except for Deepal and Sanjiva? Again I agree there was no vote, but that
| did not happen....
|
| Thanks,
| Ruwan
|
| On Wed, Apr 23, 2008 at 2:24 AM, Davanum Srinivas <da...@gmail.com> wrote:
|
| Asankha,
|
| FWIW,
|
| 1) I see a +1 from Deepal and Dr. Sanjiva
| 2) No one did a -1
| 3) There was no VOTE
|
| So, where's the beef? AFAICT, No one objected to someone else doing the
| work :)
|
| So all i can see is an implicit and not to mention unilateral decision to
| fork the code and leave the copy in Axis2 stale.
|
| -- dims
|
| Asankha C. Perera wrote:
| | Check this thread
| |
| <
|
http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/%3c672a01200710022224t1e100d77gb83e7bcfeeb8ad94@mail.gmail.com%3e
|
| | as well titled "Getting axis2 transport out from the kernel"
| |
| | asankha
| |
| | Davanum Srinivas wrote:
| |> Ruwan,
| |>
| |> All i see is some discussion, which happens on a topic
| |>
| |> http://marc.info/?t=119684680300006&r=1&w=3
| |>
| |> - Where is the push back? From who?
| |> - Where is the VOTE?
| |> - Where is a -1?
| |>
| |> thanks,
| |> dims
| |
| |
|>
- ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
|>
|>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDlTLgNg6eWEDv1kRAm3XAJ0clhpFE1S1QLp1MrtCQxn62PpMcQCfdyCk
L7p0EV6pDt3zy5FYoPeQZtM=
=aCzB
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
Dims,
If the axis2 community had agreed to do that then one of the core members of
the axis2 team should do that, (we don't want to move the code inside axis2
and mess with your project, would you like me moving the transports out from
axis2 kernel??? also with the objections in that thread), but as you can
clearly see there were tons of objections and no one was ready to move them
out except for Deepal and Sanjiva? Again I agree there was no vote, but that
did not happen....
Thanks,
Ruwan
On Wed, Apr 23, 2008 at 2:24 AM, Davanum Srinivas <da...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Asankha,
>
> FWIW,
>
> 1) I see a +1 from Deepal and Dr. Sanjiva
> 2) No one did a -1
> 3) There was no VOTE
>
> So, where's the beef? AFAICT, No one objected to someone else doing the
> work :)
>
> So all i can see is an implicit and not to mention unilateral decision to
> fork the code and leave the copy in Axis2 stale.
>
> - -- dims
>
> Asankha C. Perera wrote:
> | Check this thread
> |
> <
> http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/%3c672a01200710022224t1e100d77gb83e7bcfeeb8ad94@mail.gmail.com%3e
> >
>
>
> | as well titled "Getting axis2 transport out from the kernel"
> |
> | asankha
> |
> | Davanum Srinivas wrote:
> |> Ruwan,
> |>
> |> All i see is some discussion, which happens on a topic
> |>
> |> http://marc.info/?t=119684680300006&r=1&w=3
> |>
> |> - Where is the push back? From who?
> |> - Where is the VOTE?
> |> - Where is a -1?
> |>
> |> thanks,
> |> dims
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDlCRgNg6eWEDv1kRAuSDAKCtn+NYtfbFSiR/qXd4wncGymFhywCeNBjU
> 86McoG01Pp5nJ2ahQFYJrk0=
> =kPhE
>
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Asankha,
FWIW,
1) I see a +1 from Deepal and Dr. Sanjiva
2) No one did a -1
3) There was no VOTE
So, where's the beef? AFAICT, No one objected to someone else doing the work :)
So all i can see is an implicit and not to mention unilateral decision to fork the code and leave the copy in Axis2 stale.
- -- dims
Asankha C. Perera wrote:
| Check this thread
|
<http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/%3c672a01200710022224t1e100d77gb83e7bcfeeb8ad94@mail.gmail.com%3e>
| as well titled "Getting axis2 transport out from the kernel"
|
| asankha
|
| Davanum Srinivas wrote:
|> Ruwan,
|>
|> All i see is some discussion, which happens on a topic
|>
|> http://marc.info/?t=119684680300006&r=1&w=3
|>
|> - Where is the push back? From who?
|> - Where is the VOTE?
|> - Where is a -1?
|>
|> thanks,
|> dims
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDlCRgNg6eWEDv1kRAuSDAKCtn+NYtfbFSiR/qXd4wncGymFhywCeNBjU
86McoG01Pp5nJ2ahQFYJrk0=
=kPhE
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Check this thread
<http://mail-archives.apache.org/mod_mbox/synapse-dev/200710.mbox/%3c672a01200710022224t1e100d77gb83e7bcfeeb8ad94@mail.gmail.com%3e>
as well titled "Getting axis2 transport out from the kernel"
asankha
Davanum Srinivas wrote:
> Ruwan,
>
> All i see is some discussion, which happens on a topic
>
> http://marc.info/?t=119684680300006&r=1&w=3
>
> - Where is the push back? From who?
> - Where is the VOTE?
> - Where is a -1?
>
> thanks,
> dims
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ruwan,
All i see is some discussion, which happens on a topic
http://marc.info/?t=119684680300006&r=1&w=3
- - Where is the push back? From who?
- - Where is the VOTE?
- - Where is a -1?
thanks,
dims
Ruwan Linton wrote:
| Dims,
|
| I couldn't find this on the axis2 mail archives, that thread was having the
| subject "Improvement to mail transport from a Synapse use case" and posted
| by saminda to the axis-dev.
|
| Here is the relevant thread on Synapse [
| http://mail-archives.apache.org/mod_mbox/synapse-user/200712.mbox/thread]
|
| Thanks,
| Ruwan
|
| On Wed, Apr 23, 2008 at 12:16 AM, Davanum Srinivas <da...@gmail.com>
| wrote:
| Ruwan,
|
| How about a pointer to a public discussion on why SMTP Transport changes
|> were debated? :)
| -- dims
|
|
|
|
| Ruwan Linton wrote:
| | Glen,
| |
| | I agree with you. But my concern is the history. That is, when ever we
| | (synapse) wanted some transport specific feature for synapse to be added
|> to
| | axis2 transports axis2 community was not accepting them due to many
|> reasons
| | most of them are valid for web services, but from the synapse point of
|> view,
| | we do not need to (and should not) bound to the web services. Isn't it?
| |
| | This behavior is affecting the evolution of synapse and that is why we
|> went
| | ahead and developed our own transports. (Best example is the SMTP
|> transport)
| |
| | Thanks,
| | Ruwan
| |
| | On Tue, Apr 22, 2008 at 11:48 PM, Glen Daniels <gl...@thoughtcraft.com>
| | wrote:
| |
| |> Hi Ruwan:
| |>
| |> If a given transport really only has relevance in the Synapse
|> environment,
| |> then of course that transport has no need to exist outside Synapse.
|> But if
| |> a transport is generically useful, I'd prefer to see it somewhere in WS
| |> space as opposed to specifically within Synapse. And if some generic
| |> transport needs tweaking in particular ways for Synapse, then those
|> ways
| |> should be exposed as configuration or plug-points on the transport,
|> which
| |> get exercised by Synapse (but also tested in the transport build).
|> Example
| |> - the nhttp transport could just include a callback property which, if
|> set,
| |> passes the 202 to a listener and ignores it otherwise (perhaps that's
| |> exactly the way it works). In the SMTP case, we should discuss what
| |> happens, but again I don't see any issue with making a clean and useful
| |> general SMTP transport - why should there need to be two of them??
| |>
| |> Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
| |> Axis2. They're not a Synapse user and are not interested in
|> downloading
| |> Synapse. I want to make sure that this user can easily locate,
|> download,
| |> and install the transport they want. At the same time I want the Axis2
|> and
| |> the Synapse communities both sharing their skills to make the best set
|> of
| |> transports available for Axis2 and of course Axis2+Synapse.
| |>
| |> I'm not wedded to the details, as long as we can make that happen. It
| |> seems to me right now that ws-commons/transports is a better way to do
|> this
| |> than having lots of extension transports in Synapse, but I'm willing to
|> be
| |> convinced otherwise.
| |>
| |> Thanks,
| |> --Glen
| |>
| |> Ruwan Linton wrote:
| |>
| |>> I forgot to mention that, of cause one can use these transports with
| |>> knowing the limitations and issues of those, when working directly
|> with
| |>> axis2
| |>>
| |>> Thanks,
| |>> Ruwan
| |>>
| |>> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com
|> <mailto:
| |>> ruwan.linton@gmail.com>> wrote:
| |>>
| |>> Hi Dims, Glen and all,
| |>>
| |>> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
| |>> <davanum@gmail.com <ma...@gmail.com>> wrote:
| |>>
|
|
|
| | Glen,
| |
| | At this point, Can we please agree that it's better for the
| | people who actually work on it have their way :)
| |
| |
| |>>> +1 for this idea ... and one more thing is that;
| |
| |>>> Although the transports which resides under synapse code base are
| |>>> just axis2 transports, there are some special cases that synapse
| |>>> needs from its transports. For example;
| |
| | * nhttp transport requires 202 Accepted HTTP messages to be
| | injected inside to synapse so that it can complete mediation
| | of one-way messages as well as we need those messages to be
| | injected on the separateListener case, where as axis2 should
| | just neglect those HTTP messages.
| | * Same with 500 Internal Server Error on nhttp
| | * smtp transport requires to treat all the Cc headers and Cc the
| | message to all the specified addresses (we have discussed this
| | earlier on axis2 and this is wrong according to the WS-MEPs,
| | because there are many outs)
| |
| |>>> There are a number of synapse specific logic inside synapse
| |>>> transports, because synapse is not purely bound to WS space, but
|> it
| |>>> is a mediation framework (ESB) which should support most of the
| |>>> other scenarios going out of the WS space. There for these
| |>>> transports may not directly work with axis2 and it is not at all a
| |>>> good idea to move them out from synapse code base.
| |
| |>>> Thanks,
| |>>> Ruwan
| |
| |
| |
| | thanks,
| | dims
| |
| |
| | Glen Daniels wrote:
| | | Asankha C. Perera wrote:
| | |> Dims
| | |>> - there should not be stale copies
| | |>> - people who work on them should work where they want to.
| | |> +1 to both!
| | |
| | | Agreed - I'd just prefer people wanted to work on them under
| | WS/Axis. :)
| | |
| | |> I'd like to maintain these under Synapse.. We wrote these
| | transports
| | |> primarily for use by Synapse, and now we have JMS,
| | NIO-HTTP/S, Mail,
| | |> VFS (File), FIX and AMQP already.. These belong to a separate
| | Maven
| | |> module thats published to the Apache snapshots and Maven
| |>>> Central
| | |> repos, and
| | |
| | | Hm. So this is a bit of a separate conversation, but *each*
| | of the
| | | transports should be its own deployable artifact. If I want
| | the AMQP
| | | transport for some work I'm doing, I don't want to bother
| | downloading
| | | all the others.... Wherever they end up we should fix that!!
| | |
| | |> this JAR does not depend on the Synapse codebase at all.
| | Anyone who
| | |> wishes to use these can do so without any problems
| | whatsoever, and
| | |> raise JIRA's for bugs/enhancements where the code is actually
| | maintained.
| | |
| | | Yeah. I just think this makes a lot more sense under WS.
| | |
| | |>> | | These transports (JMS, NIO, whatever) are going to be
| | generally
| | |>> useful to any Axis2 user, so why make them go look in
| |>>> Synapse's
| | |>> codebase for them?
| | |> I agree,.. however these transports were written by the
| |>>> Synapse
| | |> community for primary use by them. So instead of asking them
| |>>> to
| | |> maintain the code they write somewhere else - for the
| | convenience of
| | |> the secondary users, why not clearly document the available
| | options
| | |> under Axis2 and where one could download these extension
| | transports
| | |> developed by the Synapse community?
| | |
| | | Sure, I'm not saying that wouldn't work - what's really
| | important to me
| | | is that Axis2 users get a clear picture of the available
| | transports when
| | | they download Axis2 and use our website. This is both to avoid
| | | duplication of effort and to enable users to use the richest
| | set of
| | | components available. It seems to me that the most natural way
| |>>> to
| | | achieve this is to contribute new transports to ws-commons or
| | Axis2.
| | |
| | | Also consider this - wouldn't it be cool to be able to run the
| | Axis2
| | | test suite (which is presumably much more comprehensive than
| | Synapse's
| | | testing of Axis2) over each of the transports that Synapse
| | originally
| | | built? I would think that might demonstrate some issues that
| | Synapse
| | | itself might not find, thus enabling the transports to be
| | improved.
| | |
| | | But if the community wants to keep developing these under
| | Synapse, then
| | | we definitely need some pointers in the Axis2 code and web
| | pages, and
| | | those pointers need to be maintained.
| | |
| | | Thanks,
| | | --Glen
| | |
| | |
| |
| |>>>
|> ---------------------------------------------------------------------
| | | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| | <ma...@ws.apache.org>
| | | For additional commands, e-mail: axis-dev-help@ws.apache.org
| | <ma...@ws.apache.org>
| | |
| |>>
| |>>
| |>>
|
| |>> ---------------------------------------------------------------------
| To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| <ma...@ws.apache.org>
| For additional commands, e-mail: axis-dev-help@ws.apache.org
| <ma...@ws.apache.org>
| |>>
| |>>
| |>>
| |>>
| |>> -- Ruwan Linton
| |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
| |>>
| |>>
| |>>
| |>> --
| |>> Ruwan Linton
| |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
| |>>
| |> ---------------------------------------------------------------------
| |> 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
|>
|>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD4DBQFIDkDSgNg6eWEDv1kRAgbhAJ4hEqtqTp7Xc2C2SoKRp7x85H8lHQCY144n
UEgjToYwR6teYulTJdfFIA==
=lhqw
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
Dims,
I couldn't find this on the axis2 mail archives, that thread was having the
subject "Improvement to mail transport from a Synapse use case" and posted
by saminda to the axis-dev.
Here is the relevant thread on Synapse [
http://mail-archives.apache.org/mod_mbox/synapse-user/200712.mbox/thread]
Thanks,
Ruwan
On Wed, Apr 23, 2008 at 12:16 AM, Davanum Srinivas <da...@gmail.com>
wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Ruwan,
>
> How about a pointer to a public discussion on why SMTP Transport changes
were debated? :)
>
> - -- dims
>
>
>
>
> Ruwan Linton wrote:
> | Glen,
> |
> | I agree with you. But my concern is the history. That is, when ever we
> | (synapse) wanted some transport specific feature for synapse to be added
to
> | axis2 transports axis2 community was not accepting them due to many
reasons
> | most of them are valid for web services, but from the synapse point of
view,
> | we do not need to (and should not) bound to the web services. Isn't it?
> |
> | This behavior is affecting the evolution of synapse and that is why we
went
> | ahead and developed our own transports. (Best example is the SMTP
transport)
> |
> | Thanks,
> | Ruwan
> |
> | On Tue, Apr 22, 2008 at 11:48 PM, Glen Daniels <gl...@thoughtcraft.com>
> | wrote:
> |
> |> Hi Ruwan:
> |>
> |> If a given transport really only has relevance in the Synapse
environment,
> |> then of course that transport has no need to exist outside Synapse.
But if
> |> a transport is generically useful, I'd prefer to see it somewhere in WS
> |> space as opposed to specifically within Synapse. And if some generic
> |> transport needs tweaking in particular ways for Synapse, then those
ways
> |> should be exposed as configuration or plug-points on the transport,
which
> |> get exercised by Synapse (but also tested in the transport build).
Example
> |> - the nhttp transport could just include a callback property which, if
set,
> |> passes the 202 to a listener and ignores it otherwise (perhaps that's
> |> exactly the way it works). In the SMTP case, we should discuss what
> |> happens, but again I don't see any issue with making a clean and useful
> |> general SMTP transport - why should there need to be two of them??
> |>
> |> Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
> |> Axis2. They're not a Synapse user and are not interested in
downloading
> |> Synapse. I want to make sure that this user can easily locate,
download,
> |> and install the transport they want. At the same time I want the Axis2
and
> |> the Synapse communities both sharing their skills to make the best set
of
> |> transports available for Axis2 and of course Axis2+Synapse.
> |>
> |> I'm not wedded to the details, as long as we can make that happen. It
> |> seems to me right now that ws-commons/transports is a better way to do
this
> |> than having lots of extension transports in Synapse, but I'm willing to
be
> |> convinced otherwise.
> |>
> |> Thanks,
> |> --Glen
> |>
> |> Ruwan Linton wrote:
> |>
> |>> I forgot to mention that, of cause one can use these transports with
> |>> knowing the limitations and issues of those, when working directly
with
> |>> axis2
> |>>
> |>> Thanks,
> |>> Ruwan
> |>>
> |>> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com
<mailto:
> |>> ruwan.linton@gmail.com>> wrote:
> |>>
> |>> Hi Dims, Glen and all,
> |>>
> |>> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
> |>> <davanum@gmail.com <ma...@gmail.com>> wrote:
> |>>
>
>
>
> | Glen,
> |
> | At this point, Can we please agree that it's better for the
> | people who actually work on it have their way :)
> |
> |
> |>>> +1 for this idea ... and one more thing is that;
> |
> |>>> Although the transports which resides under synapse code base are
> |>>> just axis2 transports, there are some special cases that synapse
> |>>> needs from its transports. For example;
> |
> | * nhttp transport requires 202 Accepted HTTP messages to be
> | injected inside to synapse so that it can complete mediation
> | of one-way messages as well as we need those messages to be
> | injected on the separateListener case, where as axis2 should
> | just neglect those HTTP messages.
> | * Same with 500 Internal Server Error on nhttp
> | * smtp transport requires to treat all the Cc headers and Cc the
> | message to all the specified addresses (we have discussed this
> | earlier on axis2 and this is wrong according to the WS-MEPs,
> | because there are many outs)
> |
> |>>> There are a number of synapse specific logic inside synapse
> |>>> transports, because synapse is not purely bound to WS space, but
it
> |>>> is a mediation framework (ESB) which should support most of the
> |>>> other scenarios going out of the WS space. There for these
> |>>> transports may not directly work with axis2 and it is not at all a
> |>>> good idea to move them out from synapse code base.
> |
> |>>> Thanks,
> |>>> Ruwan
> |
> |
> |
> | thanks,
> | dims
> |
> |
> | Glen Daniels wrote:
> | | Asankha C. Perera wrote:
> | |> Dims
> | |>> - there should not be stale copies
> | |>> - people who work on them should work where they want to.
> | |> +1 to both!
> | |
> | | Agreed - I'd just prefer people wanted to work on them under
> | WS/Axis. :)
> | |
> | |> I'd like to maintain these under Synapse.. We wrote these
> | transports
> | |> primarily for use by Synapse, and now we have JMS,
> | NIO-HTTP/S, Mail,
> | |> VFS (File), FIX and AMQP already.. These belong to a separate
> | Maven
> | |> module thats published to the Apache snapshots and Maven
> |>>> Central
> | |> repos, and
> | |
> | | Hm. So this is a bit of a separate conversation, but *each*
> | of the
> | | transports should be its own deployable artifact. If I want
> | the AMQP
> | | transport for some work I'm doing, I don't want to bother
> | downloading
> | | all the others.... Wherever they end up we should fix that!!
> | |
> | |> this JAR does not depend on the Synapse codebase at all.
> | Anyone who
> | |> wishes to use these can do so without any problems
> | whatsoever, and
> | |> raise JIRA's for bugs/enhancements where the code is actually
> | maintained.
> | |
> | | Yeah. I just think this makes a lot more sense under WS.
> | |
> | |>> | | These transports (JMS, NIO, whatever) are going to be
> | generally
> | |>> useful to any Axis2 user, so why make them go look in
> |>>> Synapse's
> | |>> codebase for them?
> | |> I agree,.. however these transports were written by the
> |>>> Synapse
> | |> community for primary use by them. So instead of asking them
> |>>> to
> | |> maintain the code they write somewhere else - for the
> | convenience of
> | |> the secondary users, why not clearly document the available
> | options
> | |> under Axis2 and where one could download these extension
> | transports
> | |> developed by the Synapse community?
> | |
> | | Sure, I'm not saying that wouldn't work - what's really
> | important to me
> | | is that Axis2 users get a clear picture of the available
> | transports when
> | | they download Axis2 and use our website. This is both to avoid
> | | duplication of effort and to enable users to use the richest
> | set of
> | | components available. It seems to me that the most natural way
> |>>> to
> | | achieve this is to contribute new transports to ws-commons or
> | Axis2.
> | |
> | | Also consider this - wouldn't it be cool to be able to run the
> | Axis2
> | | test suite (which is presumably much more comprehensive than
> | Synapse's
> | | testing of Axis2) over each of the transports that Synapse
> | originally
> | | built? I would think that might demonstrate some issues that
> | Synapse
> | | itself might not find, thus enabling the transports to be
> | improved.
> | |
> | | But if the community wants to keep developing these under
> | Synapse, then
> | | we definitely need some pointers in the Axis2 code and web
> | pages, and
> | | those pointers need to be maintained.
> | |
> | | Thanks,
> | | --Glen
> | |
> | |
> |
> |>>>
---------------------------------------------------------------------
> | | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> | <ma...@ws.apache.org>
> | | For additional commands, e-mail: axis-dev-help@ws.apache.org
> | <ma...@ws.apache.org>
> | |
> |>>
> |>>
> |>>
>
> |>> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> |>>
> |>>
> |>>
> |>>
> |>> -- Ruwan Linton
> |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
> |>>
> |>>
> |>>
> |>> --
> |>> Ruwan Linton
> |>> http://www.wso2.org - "Oxygenating the Web Services Platform"
> |>>
> |> ---------------------------------------------------------------------
> |> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> |> For additional commands, e-mail: axis-dev-help@ws.apache.org
> |>
> |>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDjKKgNg6eWEDv1kRAh1oAKDIPJ82Fr+3ddfsLKFVWqM4kNDIsQCdENFH
> aJEx3JawYLsf7TzW9ybtGYc=
> =8Rqf
>
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>
>
>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by David Illsley <da...@gmail.com>.
+1 since Ashanka seems up for it.
David
On Thu, Apr 24, 2008 at 6:39 AM, Deepal jayasinghe <de...@gmail.com> wrote:
>
>
> > Glen, why ws/commons/transports? Why not ws/transports??
> >
> Even though we call ws/commons/transports or ws/transports those components
> only valid for Axis2. Therefore I can not see the value of having axis2
> transport under WS [ I know I did +1 on the proposal.] :-\
>
>
>
> >
> > We've moved away from commons in Axiom etc. - that is, packages no longer
> say that and IMO that's better.
> >
> Yes. If we are moving the transport to ws , then it should not be inside
> ws/commons , should be just ws/transport. But one thing we need to keep in
> mind , we should not change the package name. If we do so we loose the
> backward compatibility again.
>
>
> With all these I think the time has come to think of moving Axis2 as TLP
> :)
>
> Thank you!
> Deepl
>
>
> >
> > Sanjiva.
> >
> > Deepal jayasinghe wrote:
> >
> > > Glen Daniels wrote:
> > >
> > > > [ Please refer to this thread for context :
> > > > http://markmail.org/message/lg3giq5kj74gjnxb
> > > > ]
> > > >
> > > >
> > > > OK, let me make a concrete proposal here.
> > > >
> > > > I hereby propose that we kick off a ws-commons "transports" project.
> As with the other ws-commons projects, this would have its own release
> schedule. All current ws-all committers would have commit rights, and we'd
> add anyone from the Synapse team that would like to work on transports, and
> isn't already a committer.
> > > >
> > > +1 for making a commons project for Axis2 transports. This will help
> both Axis2 and other dependent projects such as Synapse.
> > >
> > > >
> > > > Each transport within ws-commons Transports would be a separate
> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
> such transport would be releasable on its own with an appropriate VOTE of
> the ws-commons committers.
> > > >
> > > Personally I would like to download all the transport as a single jar ,
> but I do not mind releasing them separately as long as you give single jar
> as well.
> > >
> > > Thank you!
> > > Deepal
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> > > For additional commands, e-mail: dev-help@synapse.apache.org
> > >
> > >
> > >
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Ruwan:
Be careful to "reply all" so that dev@synapse gets cc'ed...
Ruwan Linton wrote:
> I agree with you. But my concern is the history. That is, when ever we
> (synapse) wanted some transport specific feature for synapse to be added
> to axis2 transports axis2 community was not accepting them due to many
> reasons most of them are valid for web services, but from the synapse
> point of view, we do not need to (and should not) bound to the web
> services. Isn't it?
I don't think so - Axis2 supports REST-style invocations as well, right?
Let me put it this way... if Synapse is using these transport *as* Axis2
transports (i.e. plugging them in via axis2.xml, etc), then they *are*
Axis2 transports regardless of whether you're using them for SOAP or not
on the wire. If Synapse had some completely different mechanism for
installing transports that doesn't go through Axis2 at ALL, then that
would clearly be very different (it doesn't, does it?).
> This behavior is affecting the evolution of synapse and that is why we
> went ahead and developed our own transports. (Best example is the SMTP
> transport)
I agree with dims - I'd like to see the conversations you're referring
to. If there is a community issue here, let's work it out - I'd rather
do the right thing (esp if everyone actually agrees :)) than have a
suboptimal solution which masks a problem we should be solving.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Ruwan:
Be careful to "reply all" so that dev@synapse gets cc'ed...
Ruwan Linton wrote:
> I agree with you. But my concern is the history. That is, when ever we
> (synapse) wanted some transport specific feature for synapse to be added
> to axis2 transports axis2 community was not accepting them due to many
> reasons most of them are valid for web services, but from the synapse
> point of view, we do not need to (and should not) bound to the web
> services. Isn't it?
I don't think so - Axis2 supports REST-style invocations as well, right?
Let me put it this way... if Synapse is using these transport *as* Axis2
transports (i.e. plugging them in via axis2.xml, etc), then they *are*
Axis2 transports regardless of whether you're using them for SOAP or not
on the wire. If Synapse had some completely different mechanism for
installing transports that doesn't go through Axis2 at ALL, then that
would clearly be very different (it doesn't, does it?).
> This behavior is affecting the evolution of synapse and that is why we
> went ahead and developed our own transports. (Best example is the SMTP
> transport)
I agree with dims - I'd like to see the conversations you're referring
to. If there is a community issue here, let's work it out - I'd rather
do the right thing (esp if everyone actually agrees :)) than have a
suboptimal solution which masks a problem we should be solving.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Ruwan,
How about a pointer to a public discussion on why SMTP Transport changes were debated? :)
- -- dims
Ruwan Linton wrote:
| Glen,
|
| I agree with you. But my concern is the history. That is, when ever we
| (synapse) wanted some transport specific feature for synapse to be added to
| axis2 transports axis2 community was not accepting them due to many reasons
| most of them are valid for web services, but from the synapse point of view,
| we do not need to (and should not) bound to the web services. Isn't it?
|
| This behavior is affecting the evolution of synapse and that is why we went
| ahead and developed our own transports. (Best example is the SMTP transport)
|
| Thanks,
| Ruwan
|
| On Tue, Apr 22, 2008 at 11:48 PM, Glen Daniels <gl...@thoughtcraft.com>
| wrote:
|
|> Hi Ruwan:
|>
|> If a given transport really only has relevance in the Synapse environment,
|> then of course that transport has no need to exist outside Synapse. But if
|> a transport is generically useful, I'd prefer to see it somewhere in WS
|> space as opposed to specifically within Synapse. And if some generic
|> transport needs tweaking in particular ways for Synapse, then those ways
|> should be exposed as configuration or plug-points on the transport, which
|> get exercised by Synapse (but also tested in the transport build). Example
|> - the nhttp transport could just include a callback property which, if set,
|> passes the 202 to a listener and ignores it otherwise (perhaps that's
|> exactly the way it works). In the SMTP case, we should discuss what
|> happens, but again I don't see any issue with making a clean and useful
|> general SMTP transport - why should there need to be two of them??
|>
|> Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
|> Axis2. They're not a Synapse user and are not interested in downloading
|> Synapse. I want to make sure that this user can easily locate, download,
|> and install the transport they want. At the same time I want the Axis2 and
|> the Synapse communities both sharing their skills to make the best set of
|> transports available for Axis2 and of course Axis2+Synapse.
|>
|> I'm not wedded to the details, as long as we can make that happen. It
|> seems to me right now that ws-commons/transports is a better way to do this
|> than having lots of extension transports in Synapse, but I'm willing to be
|> convinced otherwise.
|>
|> Thanks,
|> --Glen
|>
|> Ruwan Linton wrote:
|>
|>> I forgot to mention that, of cause one can use these transports with
|>> knowing the limitations and issues of those, when working directly with
|>> axis2
|>>
|>> Thanks,
|>> Ruwan
|>>
|>> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com<mailto:
|>> ruwan.linton@gmail.com>> wrote:
|>>
|>> Hi Dims, Glen and all,
|>>
|>> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
|>> <davanum@gmail.com <ma...@gmail.com>> wrote:
|>>
| Glen,
|
| At this point, Can we please agree that it's better for the
| people who actually work on it have their way :)
|
|
|>>> +1 for this idea ... and one more thing is that;
|
|>>> Although the transports which resides under synapse code base are
|>>> just axis2 transports, there are some special cases that synapse
|>>> needs from its transports. For example;
|
| * nhttp transport requires 202 Accepted HTTP messages to be
| injected inside to synapse so that it can complete mediation
| of one-way messages as well as we need those messages to be
| injected on the separateListener case, where as axis2 should
| just neglect those HTTP messages.
| * Same with 500 Internal Server Error on nhttp
| * smtp transport requires to treat all the Cc headers and Cc the
| message to all the specified addresses (we have discussed this
| earlier on axis2 and this is wrong according to the WS-MEPs,
| because there are many outs)
|
|>>> There are a number of synapse specific logic inside synapse
|>>> transports, because synapse is not purely bound to WS space, but it
|>>> is a mediation framework (ESB) which should support most of the
|>>> other scenarios going out of the WS space. There for these
|>>> transports may not directly work with axis2 and it is not at all a
|>>> good idea to move them out from synapse code base.
|
|>>> Thanks,
|>>> Ruwan
|
|
|
| thanks,
| dims
|
|
| Glen Daniels wrote:
| | Asankha C. Perera wrote:
| |> Dims
| |>> - there should not be stale copies
| |>> - people who work on them should work where they want to.
| |> +1 to both!
| |
| | Agreed - I'd just prefer people wanted to work on them under
| WS/Axis. :)
| |
| |> I'd like to maintain these under Synapse.. We wrote these
| transports
| |> primarily for use by Synapse, and now we have JMS,
| NIO-HTTP/S, Mail,
| |> VFS (File), FIX and AMQP already.. These belong to a separate
| Maven
| |> module thats published to the Apache snapshots and Maven
|>>> Central
| |> repos, and
| |
| | Hm. So this is a bit of a separate conversation, but *each*
| of the
| | transports should be its own deployable artifact. If I want
| the AMQP
| | transport for some work I'm doing, I don't want to bother
| downloading
| | all the others.... Wherever they end up we should fix that!!
| |
| |> this JAR does not depend on the Synapse codebase at all.
| Anyone who
| |> wishes to use these can do so without any problems
| whatsoever, and
| |> raise JIRA's for bugs/enhancements where the code is actually
| maintained.
| |
| | Yeah. I just think this makes a lot more sense under WS.
| |
| |>> | | These transports (JMS, NIO, whatever) are going to be
| generally
| |>> useful to any Axis2 user, so why make them go look in
|>>> Synapse's
| |>> codebase for them?
| |> I agree,.. however these transports were written by the
|>>> Synapse
| |> community for primary use by them. So instead of asking them
|>>> to
| |> maintain the code they write somewhere else - for the
| convenience of
| |> the secondary users, why not clearly document the available
| options
| |> under Axis2 and where one could download these extension
| transports
| |> developed by the Synapse community?
| |
| | Sure, I'm not saying that wouldn't work - what's really
| important to me
| | is that Axis2 users get a clear picture of the available
| transports when
| | they download Axis2 and use our website. This is both to avoid
| | duplication of effort and to enable users to use the richest
| set of
| | components available. It seems to me that the most natural way
|>>> to
| | achieve this is to contribute new transports to ws-commons or
| Axis2.
| |
| | Also consider this - wouldn't it be cool to be able to run the
| Axis2
| | test suite (which is presumably much more comprehensive than
| Synapse's
| | testing of Axis2) over each of the transports that Synapse
| originally
| | built? I would think that might demonstrate some issues that
| Synapse
| | itself might not find, thus enabling the transports to be
| improved.
| |
| | But if the community wants to keep developing these under
| Synapse, then
| | we definitely need some pointers in the Axis2 code and web
| pages, and
| | those pointers need to be maintained.
| |
| | Thanks,
| | --Glen
| |
| |
|
|>>> ---------------------------------------------------------------------
| | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| <ma...@ws.apache.org>
| | For additional commands, e-mail: axis-dev-help@ws.apache.org
| <ma...@ws.apache.org>
| |
|>>
|>>
|>>
|>> ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
For additional commands, e-mail: axis-dev-help@ws.apache.org
<ma...@ws.apache.org>
|>>
|>>
|>>
|>>
|>> -- Ruwan Linton
|>> http://www.wso2.org - "Oxygenating the Web Services Platform"
|>>
|>>
|>>
|>> --
|>> Ruwan Linton
|>> http://www.wso2.org - "Oxygenating the Web Services Platform"
|>>
|> ---------------------------------------------------------------------
|> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
|> For additional commands, e-mail: axis-dev-help@ws.apache.org
|>
|>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDjKKgNg6eWEDv1kRAh1oAKDIPJ82Fr+3ddfsLKFVWqM4kNDIsQCdENFH
aJEx3JawYLsf7TzW9ybtGYc=
=8Rqf
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
Glen,
I agree with you. But my concern is the history. That is, when ever we
(synapse) wanted some transport specific feature for synapse to be added to
axis2 transports axis2 community was not accepting them due to many reasons
most of them are valid for web services, but from the synapse point of view,
we do not need to (and should not) bound to the web services. Isn't it?
This behavior is affecting the evolution of synapse and that is why we went
ahead and developed our own transports. (Best example is the SMTP transport)
Thanks,
Ruwan
On Tue, Apr 22, 2008 at 11:48 PM, Glen Daniels <gl...@thoughtcraft.com>
wrote:
> Hi Ruwan:
>
> If a given transport really only has relevance in the Synapse environment,
> then of course that transport has no need to exist outside Synapse. But if
> a transport is generically useful, I'd prefer to see it somewhere in WS
> space as opposed to specifically within Synapse. And if some generic
> transport needs tweaking in particular ways for Synapse, then those ways
> should be exposed as configuration or plug-points on the transport, which
> get exercised by Synapse (but also tested in the transport build). Example
> - the nhttp transport could just include a callback property which, if set,
> passes the 202 to a listener and ignores it otherwise (perhaps that's
> exactly the way it works). In the SMTP case, we should discuss what
> happens, but again I don't see any issue with making a clean and useful
> general SMTP transport - why should there need to be two of them??
>
> Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
> Axis2. They're not a Synapse user and are not interested in downloading
> Synapse. I want to make sure that this user can easily locate, download,
> and install the transport they want. At the same time I want the Axis2 and
> the Synapse communities both sharing their skills to make the best set of
> transports available for Axis2 and of course Axis2+Synapse.
>
> I'm not wedded to the details, as long as we can make that happen. It
> seems to me right now that ws-commons/transports is a better way to do this
> than having lots of extension transports in Synapse, but I'm willing to be
> convinced otherwise.
>
> Thanks,
> --Glen
>
> Ruwan Linton wrote:
>
> > I forgot to mention that, of cause one can use these transports with
> > knowing the limitations and issues of those, when working directly with
> > axis2
> >
> > Thanks,
> > Ruwan
> >
> > On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com<mailto:
> > ruwan.linton@gmail.com>> wrote:
> >
> > Hi Dims, Glen and all,
> >
> > On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
> > <davanum@gmail.com <ma...@gmail.com>> wrote:
> >
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Glen,
> >
> > At this point, Can we please agree that it's better for the
> > people who actually work on it have their way :)
> >
> >
> > +1 for this idea ... and one more thing is that;
> >
> > Although the transports which resides under synapse code base are
> > just axis2 transports, there are some special cases that synapse
> > needs from its transports. For example;
> >
> > * nhttp transport requires 202 Accepted HTTP messages to be
> > injected inside to synapse so that it can complete mediation
> > of one-way messages as well as we need those messages to be
> > injected on the separateListener case, where as axis2 should
> > just neglect those HTTP messages.
> > * Same with 500 Internal Server Error on nhttp
> > * smtp transport requires to treat all the Cc headers and Cc the
> > message to all the specified addresses (we have discussed this
> > earlier on axis2 and this is wrong according to the WS-MEPs,
> > because there are many outs)
> >
> > There are a number of synapse specific logic inside synapse
> > transports, because synapse is not purely bound to WS space, but it
> > is a mediation framework (ESB) which should support most of the
> > other scenarios going out of the WS space. There for these
> > transports may not directly work with axis2 and it is not at all a
> > good idea to move them out from synapse code base.
> >
> > Thanks,
> > Ruwan
> >
> >
> >
> > thanks,
> > dims
> >
> >
> > Glen Daniels wrote:
> > | Asankha C. Perera wrote:
> > |> Dims
> > |>> - there should not be stale copies
> > |>> - people who work on them should work where they want to.
> > |> +1 to both!
> > |
> > | Agreed - I'd just prefer people wanted to work on them under
> > WS/Axis. :)
> > |
> > |> I'd like to maintain these under Synapse.. We wrote these
> > transports
> > |> primarily for use by Synapse, and now we have JMS,
> > NIO-HTTP/S, Mail,
> > |> VFS (File), FIX and AMQP already.. These belong to a separate
> > Maven
> > |> module thats published to the Apache snapshots and Maven
> > Central
> > |> repos, and
> > |
> > | Hm. So this is a bit of a separate conversation, but *each*
> > of the
> > | transports should be its own deployable artifact. If I want
> > the AMQP
> > | transport for some work I'm doing, I don't want to bother
> > downloading
> > | all the others.... Wherever they end up we should fix that!!
> > |
> > |> this JAR does not depend on the Synapse codebase at all.
> > Anyone who
> > |> wishes to use these can do so without any problems
> > whatsoever, and
> > |> raise JIRA's for bugs/enhancements where the code is actually
> > maintained.
> > |
> > | Yeah. I just think this makes a lot more sense under WS.
> > |
> > |>> | | These transports (JMS, NIO, whatever) are going to be
> > generally
> > |>> useful to any Axis2 user, so why make them go look in
> > Synapse's
> > |>> codebase for them?
> > |> I agree,.. however these transports were written by the
> > Synapse
> > |> community for primary use by them. So instead of asking them
> > to
> > |> maintain the code they write somewhere else - for the
> > convenience of
> > |> the secondary users, why not clearly document the available
> > options
> > |> under Axis2 and where one could download these extension
> > transports
> > |> developed by the Synapse community?
> > |
> > | Sure, I'm not saying that wouldn't work - what's really
> > important to me
> > | is that Axis2 users get a clear picture of the available
> > transports when
> > | they download Axis2 and use our website. This is both to avoid
> > | duplication of effort and to enable users to use the richest
> > set of
> > | components available. It seems to me that the most natural way
> > to
> > | achieve this is to contribute new transports to ws-commons or
> > Axis2.
> > |
> > | Also consider this - wouldn't it be cool to be able to run the
> > Axis2
> > | test suite (which is presumably much more comprehensive than
> > Synapse's
> > | testing of Axis2) over each of the transports that Synapse
> > originally
> > | built? I would think that might demonstrate some issues that
> > Synapse
> > | itself might not find, thus enabling the transports to be
> > improved.
> > |
> > | But if the community wants to keep developing these under
> > Synapse, then
> > | we definitely need some pointers in the Axis2 code and web
> > pages, and
> > | those pointers need to be maintained.
> > |
> > | Thanks,
> > | --Glen
> > |
> > |
> >
> > ---------------------------------------------------------------------
> > | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > | For additional commands, e-mail: axis-dev-help@ws.apache.org
> > <ma...@ws.apache.org>
> > |
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.5 (Cygwin)
> >
> > iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> > n+u3lNY14rCRKaSFT9s+Hw==
> > =Nw0Q
> > -----END PGP SIGNATURE-----
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > <ma...@ws.apache.org>
> >
> >
> >
> >
> > -- Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
> >
> >
> >
> > --
> > Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I agree with Glen, but would add another wrinkle. Let's make a decision and stick to it!!! Now, who wants to start a
VOTE? :)
- -- dims
Glen Daniels wrote:
| Hi Ruwan:
|
| If a given transport really only has relevance in the Synapse
| environment, then of course that transport has no need to exist outside
| Synapse. But if a transport is generically useful, I'd prefer to see it
| somewhere in WS space as opposed to specifically within Synapse. And if
| some generic transport needs tweaking in particular ways for Synapse,
| then those ways should be exposed as configuration or plug-points on the
| transport, which get exercised by Synapse (but also tested in the
| transport build). Example - the nhttp transport could just include a
| callback property which, if set, passes the 202 to a listener and
| ignores it otherwise (perhaps that's exactly the way it works). In the
| SMTP case, we should discuss what happens, but again I don't see any
| issue with making a clean and useful general SMTP transport - why should
| there need to be two of them??
|
| Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
| Axis2. They're not a Synapse user and are not interested in downloading
| Synapse. I want to make sure that this user can easily locate,
| download, and install the transport they want. At the same time I want
| the Axis2 and the Synapse communities both sharing their skills to make
| the best set of transports available for Axis2 and of course Axis2+Synapse.
|
| I'm not wedded to the details, as long as we can make that happen. It
| seems to me right now that ws-commons/transports is a better way to do
| this than having lots of extension transports in Synapse, but I'm
| willing to be convinced otherwise.
|
| Thanks,
| --Glen
|
| Ruwan Linton wrote:
|> I forgot to mention that, of cause one can use these transports with
|> knowing the limitations and issues of those, when working directly
|> with axis2
|>
|> Thanks,
|> Ruwan
|>
|> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com
|> <ma...@gmail.com>> wrote:
|>
|> Hi Dims, Glen and all,
|>
|> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
|> <davanum@gmail.com <ma...@gmail.com>> wrote:
|>
| Glen,
|
| At this point, Can we please agree that it's better for the
| people who actually work on it have their way :)
|
|
|>> +1 for this idea ... and one more thing is that;
|
|>> Although the transports which resides under synapse code base are
|>> just axis2 transports, there are some special cases that synapse
|>> needs from its transports. For example;
|
| * nhttp transport requires 202 Accepted HTTP messages to be
| injected inside to synapse so that it can complete mediation
| of one-way messages as well as we need those messages to be
| injected on the separateListener case, where as axis2 should
| just neglect those HTTP messages.
| * Same with 500 Internal Server Error on nhttp
| * smtp transport requires to treat all the Cc headers and Cc the
| message to all the specified addresses (we have discussed this
| earlier on axis2 and this is wrong according to the WS-MEPs,
| because there are many outs)
|
|>> There are a number of synapse specific logic inside synapse
|>> transports, because synapse is not purely bound to WS space, but it
|>> is a mediation framework (ESB) which should support most of the
|>> other scenarios going out of the WS space. There for these
|>> transports may not directly work with axis2 and it is not at all a
|>> good idea to move them out from synapse code base.
|
|>> Thanks,
|>> Ruwan
|>>
|
|
| thanks,
| dims
|
|
| Glen Daniels wrote:
| | Asankha C. Perera wrote:
| |> Dims
| |>> - there should not be stale copies
| |>> - people who work on them should work where they want to.
| |> +1 to both!
| |
| | Agreed - I'd just prefer people wanted to work on them under
| WS/Axis. :)
| |
| |> I'd like to maintain these under Synapse.. We wrote these
| transports
| |> primarily for use by Synapse, and now we have JMS,
| NIO-HTTP/S, Mail,
| |> VFS (File), FIX and AMQP already.. These belong to a separate
| Maven
| |> module thats published to the Apache snapshots and Maven
|>> Central
| |> repos, and
| |
| | Hm. So this is a bit of a separate conversation, but *each*
| of the
| | transports should be its own deployable artifact. If I want
| the AMQP
| | transport for some work I'm doing, I don't want to bother
| downloading
| | all the others.... Wherever they end up we should fix that!!
| |
| |> this JAR does not depend on the Synapse codebase at all.
| Anyone who
| |> wishes to use these can do so without any problems
| whatsoever, and
| |> raise JIRA's for bugs/enhancements where the code is actually
| maintained.
| |
| | Yeah. I just think this makes a lot more sense under WS.
| |
| |>> | | These transports (JMS, NIO, whatever) are going to be
| generally
| |>> useful to any Axis2 user, so why make them go look in
|>> Synapse's
| |>> codebase for them?
| |> I agree,.. however these transports were written by the
|>> Synapse
| |> community for primary use by them. So instead of asking
|>> them to
| |> maintain the code they write somewhere else - for the
| convenience of
| |> the secondary users, why not clearly document the available
| options
| |> under Axis2 and where one could download these extension
| transports
| |> developed by the Synapse community?
| |
| | Sure, I'm not saying that wouldn't work - what's really
| important to me
| | is that Axis2 users get a clear picture of the available
| transports when
| | they download Axis2 and use our website. This is both to avoid
| | duplication of effort and to enable users to use the richest
| set of
| | components available. It seems to me that the most natural
|>> way to
| | achieve this is to contribute new transports to ws-commons or
| Axis2.
| |
| | Also consider this - wouldn't it be cool to be able to run the
| Axis2
| | test suite (which is presumably much more comprehensive than
| Synapse's
| | testing of Axis2) over each of the transports that Synapse
| originally
| | built? I would think that might demonstrate some issues that
| Synapse
| | itself might not find, thus enabling the transports to be
| improved.
| |
| | But if the community wants to keep developing these under
| Synapse, then
| | we definitely need some pointers in the Axis2 code and web
| pages, and
| | those pointers need to be maintained.
| |
| | Thanks,
| | --Glen
| |
| |
|
|>> ---------------------------------------------------------------------
| | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| <ma...@ws.apache.org>
| | For additional commands, e-mail: axis-dev-help@ws.apache.org
| <ma...@ws.apache.org>
| |
|>
|>
|> ---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
<ma...@ws.apache.org>
For additional commands, e-mail: axis-dev-help@ws.apache.org
<ma...@ws.apache.org>
|>
|>
|>
|>
|> -- Ruwan Linton
|> http://www.wso2.org - "Oxygenating the Web Services Platform"
|>
|>
|>
|> --
|> Ruwan Linton
|> http://www.wso2.org - "Oxygenating the Web Services Platform"
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| For additional commands, e-mail: axis-dev-help@ws.apache.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDiy9gNg6eWEDv1kRAkj7AKC7o3dhpnCmS5Pxjo23O/1McEqzeQCgyD0B
+BQwhpVIwIT+EjQ/vCS9G1Y=
=EzIW
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Ruwan:
If a given transport really only has relevance in the Synapse
environment, then of course that transport has no need to exist outside
Synapse. But if a transport is generically useful, I'd prefer to see it
somewhere in WS space as opposed to specifically within Synapse. And if
some generic transport needs tweaking in particular ways for Synapse,
then those ways should be exposed as configuration or plug-points on the
transport, which get exercised by Synapse (but also tested in the
transport build). Example - the nhttp transport could just include a
callback property which, if set, passes the 202 to a listener and
ignores it otherwise (perhaps that's exactly the way it works). In the
SMTP case, we should discuss what happens, but again I don't see any
issue with making a clean and useful general SMTP transport - why should
there need to be two of them??
Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
Axis2. They're not a Synapse user and are not interested in downloading
Synapse. I want to make sure that this user can easily locate,
download, and install the transport they want. At the same time I want
the Axis2 and the Synapse communities both sharing their skills to make
the best set of transports available for Axis2 and of course Axis2+Synapse.
I'm not wedded to the details, as long as we can make that happen. It
seems to me right now that ws-commons/transports is a better way to do
this than having lots of extension transports in Synapse, but I'm
willing to be convinced otherwise.
Thanks,
--Glen
Ruwan Linton wrote:
> I forgot to mention that, of cause one can use these transports with
> knowing the limitations and issues of those, when working directly with
> axis2
>
> Thanks,
> Ruwan
>
> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hi Dims, Glen and all,
>
> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
> <davanum@gmail.com <ma...@gmail.com>> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> At this point, Can we please agree that it's better for the
> people who actually work on it have their way :)
>
>
> +1 for this idea ... and one more thing is that;
>
> Although the transports which resides under synapse code base are
> just axis2 transports, there are some special cases that synapse
> needs from its transports. For example;
>
> * nhttp transport requires 202 Accepted HTTP messages to be
> injected inside to synapse so that it can complete mediation
> of one-way messages as well as we need those messages to be
> injected on the separateListener case, where as axis2 should
> just neglect those HTTP messages.
> * Same with 500 Internal Server Error on nhttp
> * smtp transport requires to treat all the Cc headers and Cc the
> message to all the specified addresses (we have discussed this
> earlier on axis2 and this is wrong according to the WS-MEPs,
> because there are many outs)
>
> There are a number of synapse specific logic inside synapse
> transports, because synapse is not purely bound to WS space, but it
> is a mediation framework (ESB) which should support most of the
> other scenarios going out of the WS space. There for these
> transports may not directly work with axis2 and it is not at all a
> good idea to move them out from synapse code base.
>
> Thanks,
> Ruwan
>
>
>
>
> thanks,
> dims
>
>
> Glen Daniels wrote:
> | Asankha C. Perera wrote:
> |> Dims
> |>> - there should not be stale copies
> |>> - people who work on them should work where they want to.
> |> +1 to both!
> |
> | Agreed - I'd just prefer people wanted to work on them under
> WS/Axis. :)
> |
> |> I'd like to maintain these under Synapse.. We wrote these
> transports
> |> primarily for use by Synapse, and now we have JMS,
> NIO-HTTP/S, Mail,
> |> VFS (File), FIX and AMQP already.. These belong to a separate
> Maven
> |> module thats published to the Apache snapshots and Maven Central
> |> repos, and
> |
> | Hm. So this is a bit of a separate conversation, but *each*
> of the
> | transports should be its own deployable artifact. If I want
> the AMQP
> | transport for some work I'm doing, I don't want to bother
> downloading
> | all the others.... Wherever they end up we should fix that!!
> |
> |> this JAR does not depend on the Synapse codebase at all.
> Anyone who
> |> wishes to use these can do so without any problems
> whatsoever, and
> |> raise JIRA's for bugs/enhancements where the code is actually
> maintained.
> |
> | Yeah. I just think this makes a lot more sense under WS.
> |
> |>> | | These transports (JMS, NIO, whatever) are going to be
> generally
> |>> useful to any Axis2 user, so why make them go look in Synapse's
> |>> codebase for them?
> |> I agree,.. however these transports were written by the Synapse
> |> community for primary use by them. So instead of asking them to
> |> maintain the code they write somewhere else - for the
> convenience of
> |> the secondary users, why not clearly document the available
> options
> |> under Axis2 and where one could download these extension
> transports
> |> developed by the Synapse community?
> |
> | Sure, I'm not saying that wouldn't work - what's really
> important to me
> | is that Axis2 users get a clear picture of the available
> transports when
> | they download Axis2 and use our website. This is both to avoid
> | duplication of effort and to enable users to use the richest
> set of
> | components available. It seems to me that the most natural way to
> | achieve this is to contribute new transports to ws-commons or
> Axis2.
> |
> | Also consider this - wouldn't it be cool to be able to run the
> Axis2
> | test suite (which is presumably much more comprehensive than
> Synapse's
> | testing of Axis2) over each of the transports that Synapse
> originally
> | built? I would think that might demonstrate some issues that
> Synapse
> | itself might not find, thus enabling the transports to be
> improved.
> |
> | But if the community wants to keep developing these under
> Synapse, then
> | we definitely need some pointers in the Axis2 code and web
> pages, and
> | those pointers need to be maintained.
> |
> | Thanks,
> | --Glen
> |
> |
> ---------------------------------------------------------------------
> | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> | For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> n+u3lNY14rCRKaSFT9s+Hw==
> =Nw0Q
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Paul Fremantle <pz...@gmail.com>.
My biggest concern with putting these in Synapse is the dependency
chain. Since the APIs are defined as part of Axis2, I think it makes
more sense for these to live in the WS space. So my preference would
be to have these (and others) in commons/transports
Paul
On Tue, Apr 22, 2008 at 6:49 PM, Ruwan Linton <ru...@gmail.com> wrote:
> I forgot to mention that, of cause one can use these transports with knowing
> the limitations and issues of those, when working directly with axis2
>
> Thanks,
> Ruwan
>
>
>
> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ru...@gmail.com>
> wrote:
>
> >
> > Hi Dims, Glen and all,
> >
> >
> >
> > On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas <da...@gmail.com>
> wrote:
> >
> > >
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Glen,
> > >
> > > At this point, Can we please agree that it's better for the people who
> actually work on it have their way :)
> >
> >
> > +1 for this idea ... and one more thing is that;
> >
> > Although the transports which resides under synapse code base are just
> axis2 transports, there are some special cases that synapse needs from its
> transports. For example;
> >
> >
> >
> > nhttp transport requires 202 Accepted HTTP messages to be injected inside
> to synapse so that it can complete mediation of one-way messages as well as
> we need those messages to be injected on the separateListener case, where as
> axis2 should just neglect those HTTP messages.
> > Same with 500 Internal Server Error on nhttp
> >
> > smtp transport requires to treat all the Cc headers and Cc the message to
> all the specified addresses (we have discussed this earlier on axis2 and
> this is wrong according to the WS-MEPs, because there are many outs)There
> are a number of synapse specific logic inside synapse transports, because
> synapse is not purely bound to WS space, but it is a mediation framework
> (ESB) which should support most of the other scenarios going out of the WS
> space. There for these transports may not directly work with axis2 and it is
> not at all a good idea to move them out from synapse code base.
> >
> > Thanks,
> > Ruwan
> >
> >
> >
> >
> > >
> > >
> > > thanks,
> > > dims
> > >
> > >
> > >
> > >
> > > Glen Daniels wrote:
> > > | Asankha C. Perera wrote:
> > > |> Dims
> > > |>> - there should not be stale copies
> > > |>> - people who work on them should work where they want to.
> > > |> +1 to both!
> > > |
> > > | Agreed - I'd just prefer people wanted to work on them under WS/Axis.
> :)
> > > |
> > > |> I'd like to maintain these under Synapse.. We wrote these transports
> > > |> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail,
> > > |> VFS (File), FIX and AMQP already.. These belong to a separate Maven
> > > |> module thats published to the Apache snapshots and Maven Central
> > > |> repos, and
> > > |
> > > | Hm. So this is a bit of a separate conversation, but *each* of the
> > > | transports should be its own deployable artifact. If I want the AMQP
> > > | transport for some work I'm doing, I don't want to bother downloading
> > > | all the others.... Wherever they end up we should fix that!!
> > > |
> > > |> this JAR does not depend on the Synapse codebase at all. Anyone who
> > > |> wishes to use these can do so without any problems whatsoever, and
> > > |> raise JIRA's for bugs/enhancements where the code is actually
> maintained.
> > > |
> > > | Yeah. I just think this makes a lot more sense under WS.
> > > |
> > > |>> | | These transports (JMS, NIO, whatever) are going to be generally
> > > |>> useful to any Axis2 user, so why make them go look in Synapse's
> > > |>> codebase for them?
> > > |> I agree,.. however these transports were written by the Synapse
> > > |> community for primary use by them. So instead of asking them to
> > > |> maintain the code they write somewhere else - for the convenience of
> > > |> the secondary users, why not clearly document the available options
> > > |> under Axis2 and where one could download these extension transports
> > > |> developed by the Synapse community?
> > > |
> > > | Sure, I'm not saying that wouldn't work - what's really important to
> me
> > > | is that Axis2 users get a clear picture of the available transports
> when
> > > | they download Axis2 and use our website. This is both to avoid
> > > | duplication of effort and to enable users to use the richest set of
> > > | components available. It seems to me that the most natural way to
> > > | achieve this is to contribute new transports to ws-commons or Axis2.
> > > |
> > > | Also consider this - wouldn't it be cool to be able to run the Axis2
> > > | test suite (which is presumably much more comprehensive than Synapse's
> > > | testing of Axis2) over each of the transports that Synapse originally
> > > | built? I would think that might demonstrate some issues that Synapse
> > > | itself might not find, thus enabling the transports to be improved.
> > > |
> > > | But if the community wants to keep developing these under Synapse,
> then
> > > | we definitely need some pointers in the Axis2 code and web pages, and
> > > | those pointers need to be maintained.
> > > |
> > > | Thanks,
> > > | --Glen
> > > |
> > > | ---------------------------------------------------------------------
> > > | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > | For additional commands, e-mail: axis-dev-help@ws.apache.org
> > > |
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.5 (Cygwin)
> > >
> > > iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> > > n+u3lNY14rCRKaSFT9s+Hw==
> > > =Nw0Q
> > > -----END PGP SIGNATURE-----
> > >
> > >
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > >
> > >
> >
> >
> >
> >
> >
> >
> > --
> > Ruwan Linton
> > http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hi Ruwan:
If a given transport really only has relevance in the Synapse
environment, then of course that transport has no need to exist outside
Synapse. But if a transport is generically useful, I'd prefer to see it
somewhere in WS space as opposed to specifically within Synapse. And if
some generic transport needs tweaking in particular ways for Synapse,
then those ways should be exposed as configuration or plug-points on the
transport, which get exercised by Synapse (but also tested in the
transport build). Example - the nhttp transport could just include a
callback property which, if set, passes the 202 to a listener and
ignores it otherwise (perhaps that's exactly the way it works). In the
SMTP case, we should discuss what happens, but again I don't see any
issue with making a clean and useful general SMTP transport - why should
there need to be two of them??
Here's my use case. Someone wants to use nhttp, or JMS, or SMTP, with
Axis2. They're not a Synapse user and are not interested in downloading
Synapse. I want to make sure that this user can easily locate,
download, and install the transport they want. At the same time I want
the Axis2 and the Synapse communities both sharing their skills to make
the best set of transports available for Axis2 and of course Axis2+Synapse.
I'm not wedded to the details, as long as we can make that happen. It
seems to me right now that ws-commons/transports is a better way to do
this than having lots of extension transports in Synapse, but I'm
willing to be convinced otherwise.
Thanks,
--Glen
Ruwan Linton wrote:
> I forgot to mention that, of cause one can use these transports with
> knowing the limitations and issues of those, when working directly with
> axis2
>
> Thanks,
> Ruwan
>
> On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ruwan.linton@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hi Dims, Glen and all,
>
> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas
> <davanum@gmail.com <ma...@gmail.com>> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> At this point, Can we please agree that it's better for the
> people who actually work on it have their way :)
>
>
> +1 for this idea ... and one more thing is that;
>
> Although the transports which resides under synapse code base are
> just axis2 transports, there are some special cases that synapse
> needs from its transports. For example;
>
> * nhttp transport requires 202 Accepted HTTP messages to be
> injected inside to synapse so that it can complete mediation
> of one-way messages as well as we need those messages to be
> injected on the separateListener case, where as axis2 should
> just neglect those HTTP messages.
> * Same with 500 Internal Server Error on nhttp
> * smtp transport requires to treat all the Cc headers and Cc the
> message to all the specified addresses (we have discussed this
> earlier on axis2 and this is wrong according to the WS-MEPs,
> because there are many outs)
>
> There are a number of synapse specific logic inside synapse
> transports, because synapse is not purely bound to WS space, but it
> is a mediation framework (ESB) which should support most of the
> other scenarios going out of the WS space. There for these
> transports may not directly work with axis2 and it is not at all a
> good idea to move them out from synapse code base.
>
> Thanks,
> Ruwan
>
>
>
>
> thanks,
> dims
>
>
> Glen Daniels wrote:
> | Asankha C. Perera wrote:
> |> Dims
> |>> - there should not be stale copies
> |>> - people who work on them should work where they want to.
> |> +1 to both!
> |
> | Agreed - I'd just prefer people wanted to work on them under
> WS/Axis. :)
> |
> |> I'd like to maintain these under Synapse.. We wrote these
> transports
> |> primarily for use by Synapse, and now we have JMS,
> NIO-HTTP/S, Mail,
> |> VFS (File), FIX and AMQP already.. These belong to a separate
> Maven
> |> module thats published to the Apache snapshots and Maven Central
> |> repos, and
> |
> | Hm. So this is a bit of a separate conversation, but *each*
> of the
> | transports should be its own deployable artifact. If I want
> the AMQP
> | transport for some work I'm doing, I don't want to bother
> downloading
> | all the others.... Wherever they end up we should fix that!!
> |
> |> this JAR does not depend on the Synapse codebase at all.
> Anyone who
> |> wishes to use these can do so without any problems
> whatsoever, and
> |> raise JIRA's for bugs/enhancements where the code is actually
> maintained.
> |
> | Yeah. I just think this makes a lot more sense under WS.
> |
> |>> | | These transports (JMS, NIO, whatever) are going to be
> generally
> |>> useful to any Axis2 user, so why make them go look in Synapse's
> |>> codebase for them?
> |> I agree,.. however these transports were written by the Synapse
> |> community for primary use by them. So instead of asking them to
> |> maintain the code they write somewhere else - for the
> convenience of
> |> the secondary users, why not clearly document the available
> options
> |> under Axis2 and where one could download these extension
> transports
> |> developed by the Synapse community?
> |
> | Sure, I'm not saying that wouldn't work - what's really
> important to me
> | is that Axis2 users get a clear picture of the available
> transports when
> | they download Axis2 and use our website. This is both to avoid
> | duplication of effort and to enable users to use the richest
> set of
> | components available. It seems to me that the most natural way to
> | achieve this is to contribute new transports to ws-commons or
> Axis2.
> |
> | Also consider this - wouldn't it be cool to be able to run the
> Axis2
> | test suite (which is presumably much more comprehensive than
> Synapse's
> | testing of Axis2) over each of the transports that Synapse
> originally
> | built? I would think that might demonstrate some issues that
> Synapse
> | itself might not find, thus enabling the transports to be
> improved.
> |
> | But if the community wants to keep developing these under
> Synapse, then
> | we definitely need some pointers in the Axis2 code and web
> pages, and
> | those pointers need to be maintained.
> |
> | Thanks,
> | --Glen
> |
> |
> ---------------------------------------------------------------------
> | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> | For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> n+u3lNY14rCRKaSFT9s+Hw==
> =Nw0Q
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
>
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
I forgot to mention that, of cause one can use these transports with knowing
the limitations and issues of those, when working directly with axis2
Thanks,
Ruwan
On Tue, Apr 22, 2008 at 11:16 PM, Ruwan Linton <ru...@gmail.com>
wrote:
> Hi Dims, Glen and all,
>
> On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas <da...@gmail.com>
> wrote:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Glen,
> >
> > At this point, Can we please agree that it's better for the people who
> > actually work on it have their way :)
>
>
> +1 for this idea ... and one more thing is that;
>
> Although the transports which resides under synapse code base are just
> axis2 transports, there are some special cases that synapse needs from its
> transports. For example;
>
> - nhttp transport requires 202 Accepted HTTP messages to be injected
> inside to synapse so that it can complete mediation of one-way messages as
> well as we need those messages to be injected on the separateListener case,
> where as axis2 should just neglect those HTTP messages.
> - Same with 500 Internal Server Error on nhttp
> - smtp transport requires to treat all the Cc headers and Cc the
> message to all the specified addresses (we have discussed this earlier on
> axis2 and this is wrong according to the WS-MEPs, because there are many
> outs)
>
> There are a number of synapse specific logic inside synapse transports,
> because synapse is not purely bound to WS space, but it is a mediation
> framework (ESB) which should support most of the other scenarios going out
> of the WS space. There for these transports may not directly work with axis2
> and it is not at all a good idea to move them out from synapse code base.
>
> Thanks,
> Ruwan
>
>
> >
> >
> > thanks,
> > dims
> >
> >
> > Glen Daniels wrote:
> > | Asankha C. Perera wrote:
> > |> Dims
> > |>> - there should not be stale copies
> > |>> - people who work on them should work where they want to.
> > |> +1 to both!
> > |
> > | Agreed - I'd just prefer people wanted to work on them under WS/Axis.
> > :)
> > |
> > |> I'd like to maintain these under Synapse.. We wrote these transports
> > |> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail,
> > |> VFS (File), FIX and AMQP already.. These belong to a separate Maven
> > |> module thats published to the Apache snapshots and Maven Central
> > |> repos, and
> > |
> > | Hm. So this is a bit of a separate conversation, but *each* of the
> > | transports should be its own deployable artifact. If I want the AMQP
> > | transport for some work I'm doing, I don't want to bother downloading
> > | all the others.... Wherever they end up we should fix that!!
> > |
> > |> this JAR does not depend on the Synapse codebase at all. Anyone who
> > |> wishes to use these can do so without any problems whatsoever, and
> > |> raise JIRA's for bugs/enhancements where the code is actually
> > maintained.
> > |
> > | Yeah. I just think this makes a lot more sense under WS.
> > |
> > |>> | | These transports (JMS, NIO, whatever) are going to be generally
> > |>> useful to any Axis2 user, so why make them go look in Synapse's
> > |>> codebase for them?
> > |> I agree,.. however these transports were written by the Synapse
> > |> community for primary use by them. So instead of asking them to
> > |> maintain the code they write somewhere else - for the convenience of
> > |> the secondary users, why not clearly document the available options
> > |> under Axis2 and where one could download these extension transports
> > |> developed by the Synapse community?
> > |
> > | Sure, I'm not saying that wouldn't work - what's really important to
> > me
> > | is that Axis2 users get a clear picture of the available transports
> > when
> > | they download Axis2 and use our website. This is both to avoid
> > | duplication of effort and to enable users to use the richest set of
> > | components available. It seems to me that the most natural way to
> > | achieve this is to contribute new transports to ws-commons or Axis2.
> > |
> > | Also consider this - wouldn't it be cool to be able to run the Axis2
> > | test suite (which is presumably much more comprehensive than Synapse's
> > | testing of Axis2) over each of the transports that Synapse originally
> > | built? I would think that might demonstrate some issues that Synapse
> > | itself might not find, thus enabling the transports to be improved.
> > |
> > | But if the community wants to keep developing these under Synapse,
> > then
> > | we definitely need some pointers in the Axis2 code and web pages, and
> > | those pointers need to be maintained.
> > |
> > | Thanks,
> > | --Glen
> > |
> > | ---------------------------------------------------------------------
> > | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > | For additional commands, e-mail: axis-dev-help@ws.apache.org
> > |
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.5 (Cygwin)
> >
> > iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> > n+u3lNY14rCRKaSFT9s+Hw==
> > =Nw0Q
> > -----END PGP SIGNATURE-----
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> >
> >
>
>
> --
> Ruwan Linton
> http://www.wso2.org - "Oxygenating the Web Services Platform"
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Ruwan Linton <ru...@gmail.com>.
Hi Dims, Glen and all,
On Tue, Apr 22, 2008 at 10:48 PM, Davanum Srinivas <da...@gmail.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> At this point, Can we please agree that it's better for the people who
> actually work on it have their way :)
+1 for this idea ... and one more thing is that;
Although the transports which resides under synapse code base are just axis2
transports, there are some special cases that synapse needs from its
transports. For example;
- nhttp transport requires 202 Accepted HTTP messages to be injected
inside to synapse so that it can complete mediation of one-way messages as
well as we need those messages to be injected on the separateListener case,
where as axis2 should just neglect those HTTP messages.
- Same with 500 Internal Server Error on nhttp
- smtp transport requires to treat all the Cc headers and Cc the
message to all the specified addresses (we have discussed this earlier on
axis2 and this is wrong according to the WS-MEPs, because there are many
outs)
There are a number of synapse specific logic inside synapse transports,
because synapse is not purely bound to WS space, but it is a mediation
framework (ESB) which should support most of the other scenarios going out
of the WS space. There for these transports may not directly work with axis2
and it is not at all a good idea to move them out from synapse code base.
Thanks,
Ruwan
>
>
> thanks,
> dims
>
>
> Glen Daniels wrote:
> | Asankha C. Perera wrote:
> |> Dims
> |>> - there should not be stale copies
> |>> - people who work on them should work where they want to.
> |> +1 to both!
> |
> | Agreed - I'd just prefer people wanted to work on them under WS/Axis. :)
> |
> |> I'd like to maintain these under Synapse.. We wrote these transports
> |> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail,
> |> VFS (File), FIX and AMQP already.. These belong to a separate Maven
> |> module thats published to the Apache snapshots and Maven Central
> |> repos, and
> |
> | Hm. So this is a bit of a separate conversation, but *each* of the
> | transports should be its own deployable artifact. If I want the AMQP
> | transport for some work I'm doing, I don't want to bother downloading
> | all the others.... Wherever they end up we should fix that!!
> |
> |> this JAR does not depend on the Synapse codebase at all. Anyone who
> |> wishes to use these can do so without any problems whatsoever, and
> |> raise JIRA's for bugs/enhancements where the code is actually
> maintained.
> |
> | Yeah. I just think this makes a lot more sense under WS.
> |
> |>> | | These transports (JMS, NIO, whatever) are going to be generally
> |>> useful to any Axis2 user, so why make them go look in Synapse's
> |>> codebase for them?
> |> I agree,.. however these transports were written by the Synapse
> |> community for primary use by them. So instead of asking them to
> |> maintain the code they write somewhere else - for the convenience of
> |> the secondary users, why not clearly document the available options
> |> under Axis2 and where one could download these extension transports
> |> developed by the Synapse community?
> |
> | Sure, I'm not saying that wouldn't work - what's really important to me
> | is that Axis2 users get a clear picture of the available transports when
> | they download Axis2 and use our website. This is both to avoid
> | duplication of effort and to enable users to use the richest set of
> | components available. It seems to me that the most natural way to
> | achieve this is to contribute new transports to ws-commons or Axis2.
> |
> | Also consider this - wouldn't it be cool to be able to run the Axis2
> | test suite (which is presumably much more comprehensive than Synapse's
> | testing of Axis2) over each of the transports that Synapse originally
> | built? I would think that might demonstrate some issues that Synapse
> | itself might not find, thus enabling the transports to be improved.
> |
> | But if the community wants to keep developing these under Synapse, then
> | we definitely need some pointers in the Axis2 code and web pages, and
> | those pointers need to be maintained.
> |
> | Thanks,
> | --Glen
> |
> | ---------------------------------------------------------------------
> | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> | For additional commands, e-mail: axis-dev-help@ws.apache.org
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> n+u3lNY14rCRKaSFT9s+Hw==
> =Nw0Q
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I agree in priniciple/theory. But IMHO, it won't work because folks who are directly involved in day-to-day efforts on
this do not agree and even if they do right now, we will back to square one in a few months one way or another.
So my VOTE is +0 as this is not practically workable.
thanks,
dims
Sanjaya Karunasena wrote:
| I am +1 for this. In terms of seperation of concerns this make lot of since.
|
| /Sanjaya
|
| On Wednesday 23 April 2008, Glen Daniels wrote:
|> [ Please refer to this thread for context :
|> http://markmail.org/message/lg3giq5kj74gjnxb
|> ]
|>
|>
|> OK, let me make a concrete proposal here.
|>
|> I hereby propose that we kick off a ws-commons "transports" project. As
|> with the other ws-commons projects, this would have its own release
|> schedule. All current ws-all committers would have commit rights, and
|> we'd add anyone from the Synapse team that would like to work on
|> transports, and isn't already a committer.
|>
|> Each transport within ws-commons Transports would be a separate
|> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
|> such transport would be releasable on its own with an appropriate VOTE
|> of the ws-commons committers.
|>
|> We'd use commons-dev and commons-user mailing lists as per usual for
|> communication, and SVN would be
|> webservices/commons/trunk/modules/transports.
|>
|> We'd get started by moving whichever transports in Axis2 and Synapse are
|> appropriate into the new source tree.
|>
|> Here's my +1. Please comment / VOTE at will.
|>
|> --Glen
|>
|> ---------------------------------------------------------------------
|> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
|> For additional commands, e-mail: axis-dev-help@ws.apache.org
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDoA8gNg6eWEDv1kRArHmAKDpA6NGXu9lY/oiGPutHI+x8r1R9wCgn7wu
VwngzO1z0zLOVRTvVL61Q9Y=
=0zQ5
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I agree in priniciple/theory. But IMHO, it won't work because folks who are directly involved in day-to-day efforts on
this do not agree and even if they do right now, we will back to square one in a few months one way or another.
So my VOTE is +0 as this is not practically workable.
thanks,
dims
Sanjaya Karunasena wrote:
| I am +1 for this. In terms of seperation of concerns this make lot of since.
|
| /Sanjaya
|
| On Wednesday 23 April 2008, Glen Daniels wrote:
|> [ Please refer to this thread for context :
|> http://markmail.org/message/lg3giq5kj74gjnxb
|> ]
|>
|>
|> OK, let me make a concrete proposal here.
|>
|> I hereby propose that we kick off a ws-commons "transports" project. As
|> with the other ws-commons projects, this would have its own release
|> schedule. All current ws-all committers would have commit rights, and
|> we'd add anyone from the Synapse team that would like to work on
|> transports, and isn't already a committer.
|>
|> Each transport within ws-commons Transports would be a separate
|> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
|> such transport would be releasable on its own with an appropriate VOTE
|> of the ws-commons committers.
|>
|> We'd use commons-dev and commons-user mailing lists as per usual for
|> communication, and SVN would be
|> webservices/commons/trunk/modules/transports.
|>
|> We'd get started by moving whichever transports in Axis2 and Synapse are
|> appropriate into the new source tree.
|>
|> Here's my +1. Please comment / VOTE at will.
|>
|> --Glen
|>
|> ---------------------------------------------------------------------
|> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
|> For additional commands, e-mail: axis-dev-help@ws.apache.org
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDoA8gNg6eWEDv1kRArHmAKDpA6NGXu9lY/oiGPutHI+x8r1R9wCgn7wu
VwngzO1z0zLOVRTvVL61Q9Y=
=0zQ5
-----END PGP SIGNATURE-----
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Sanjaya Karunasena <sa...@wso2.com>.
I am +1 for this. In terms of seperation of concerns this make lot of since.
/Sanjaya
On Wednesday 23 April 2008, Glen Daniels wrote:
> [ Please refer to this thread for context :
> http://markmail.org/message/lg3giq5kj74gjnxb
> ]
>
>
> OK, let me make a concrete proposal here.
>
> I hereby propose that we kick off a ws-commons "transports" project. As
> with the other ws-commons projects, this would have its own release
> schedule. All current ws-all committers would have commit rights, and
> we'd add anyone from the Synapse team that would like to work on
> transports, and isn't already a committer.
>
> Each transport within ws-commons Transports would be a separate
> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
> such transport would be releasable on its own with an appropriate VOTE
> of the ws-commons committers.
>
> We'd use commons-dev and commons-user mailing lists as per usual for
> communication, and SVN would be
> webservices/commons/trunk/modules/transports.
>
> We'd get started by moving whichever transports in Axis2 and Synapse are
> appropriate into the new source tree.
>
> Here's my +1. Please comment / VOTE at will.
>
> --Glen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Sanjaya Karunasena <sa...@wso2.com>.
I am +1 for this. In terms of seperation of concerns this make lot of since.
/Sanjaya
On Wednesday 23 April 2008, Glen Daniels wrote:
> [ Please refer to this thread for context :
> http://markmail.org/message/lg3giq5kj74gjnxb
> ]
>
>
> OK, let me make a concrete proposal here.
>
> I hereby propose that we kick off a ws-commons "transports" project. As
> with the other ws-commons projects, this would have its own release
> schedule. All current ws-all committers would have commit rights, and
> we'd add anyone from the Synapse team that would like to work on
> transports, and isn't already a committer.
>
> Each transport within ws-commons Transports would be a separate
> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
> such transport would be releasable on its own with an appropriate VOTE
> of the ws-commons committers.
>
> We'd use commons-dev and commons-user mailing lists as per usual for
> communication, and SVN would be
> webservices/commons/trunk/modules/transports.
>
> We'd get started by moving whichever transports in Axis2 and Synapse are
> appropriate into the new source tree.
>
> Here's my +1. Please comment / VOTE at will.
>
> --Glen
>
> ---------------------------------------------------------------------
> 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: [Axis2]WS-Commons transports project
Posted by sumedha rubasinghe <su...@apache.org>.
On Wed, Jun 25, 2008 at 12:29 AM, sumedha rubasinghe <su...@apache.org>
wrote:
> On Tue, Jun 24, 2008 at 5:10 PM, Deepal jayasinghe <de...@gmail.com>
> wrote:
>
>> Yes I found that and I am working on that now.
>>
>> axis2-kernel doesn't build anymore because it depends on classes in
>>> org.apache.axis2.transport.http.util which are no longer there.
>>>
>>> Andreas
>>>
>>> Checked with latest code from SVN (Revision: 671282).
> Build is successful.
Added missing transport jar/source files to binary/source distribution. If
you are testing, please get the latest from SVN.
/sumedha
Re: [Axis2]WS-Commons transports project
Posted by sumedha rubasinghe <su...@apache.org>.
On Wed, Jun 25, 2008 at 12:29 AM, sumedha rubasinghe <su...@apache.org>
wrote:
> On Tue, Jun 24, 2008 at 5:10 PM, Deepal jayasinghe <de...@gmail.com>
> wrote:
>
>> Yes I found that and I am working on that now.
>>
>> axis2-kernel doesn't build anymore because it depends on classes in
>>> org.apache.axis2.transport.http.util which are no longer there.
>>>
>>> Andreas
>>>
>>> Checked with latest code from SVN (Revision: 671282).
> Build is successful.
Added missing transport jar/source files to binary/source distribution. If
you are testing, please get the latest from SVN.
/sumedha
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Rajith Attapattu <ra...@gmail.com>.
+1 for this
Personally I would like to download all the transport as a single jar , but
> I do not mind releasing them separately as long as you give single jar as
> well.
I like this idea very much. I said more or less the same thing when we had a
similar disucssion a while back.
If my memory serves me right it was a debate about having to download all
the transports as part of the axis2 distribution whether one wants to use it
or not. A separate jar for each transport is a good idea in that sense. The
debate ended without any real consensus :)
Dims mentioned,
> I agree in priniciple/theory. But IMHO, it won't work because folks who
are directly involved in day-to-day efforts on
> this do not agree and even if they do right now, we will back to square
one in a few months one way or another.
I hope everybody comes to some sort of an agreement and then stick to it.
Dims is right, we need the folks who are working on it to buy in or else it
might not be all that sucessfull.
Rajith
>
>
> Thank you!
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
Re: [Axis2]WS-Commons transports project
Posted by sumedha rubasinghe <su...@apache.org>.
On Tue, Jun 24, 2008 at 5:10 PM, Deepal jayasinghe <de...@gmail.com>
wrote:
> Yes I found that and I am working on that now.
>
> axis2-kernel doesn't build anymore because it depends on classes in
>> org.apache.axis2.transport.http.util which are no longer there.
>>
>> Andreas
>>
>> Checked with latest code from SVN (Revision: 671282).
Build is successful.
/sumedha
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Rajith Attapattu <ra...@gmail.com>.
+1 for this
Personally I would like to download all the transport as a single jar , but
> I do not mind releasing them separately as long as you give single jar as
> well.
I like this idea very much. I said more or less the same thing when we had a
similar disucssion a while back.
If my memory serves me right it was a debate about having to download all
the transports as part of the axis2 distribution whether one wants to use it
or not. A separate jar for each transport is a good idea in that sense. The
debate ended without any real consensus :)
Dims mentioned,
> I agree in priniciple/theory. But IMHO, it won't work because folks who
are directly involved in day-to-day efforts on
> this do not agree and even if they do right now, we will back to square
one in a few months one way or another.
I hope everybody comes to some sort of an agreement and then stick to it.
Dims is right, we need the folks who are working on it to buy in or else it
might not be all that sucessfull.
Rajith
>
>
> Thank you!
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Regards,
Rajith Attapattu
Red Hat
http://rajith.2rlabs.com/
Re: [Axis2]WS-Commons transports project
Posted by sumedha rubasinghe <su...@apache.org>.
On Tue, Jun 24, 2008 at 5:10 PM, Deepal jayasinghe <de...@gmail.com>
wrote:
> Yes I found that and I am working on that now.
>
> axis2-kernel doesn't build anymore because it depends on classes in
>> org.apache.axis2.transport.http.util which are no longer there.
>>
>> Andreas
>>
>> Checked with latest code from SVN (Revision: 671282).
Build is successful.
/sumedha
Re: [Axis2]WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
Yes I found that and I am working on that now.
> axis2-kernel doesn't build anymore because it depends on classes in
> org.apache.axis2.transport.http.util which are no longer there.
>
> Andreas
>
> On 24 juin 08, at 13:13, Deepal jayasinghe wrote:
>
>> Hi all,
>>
>> I think most of you guys have forgotten about the proposal of moving
>> Axis2 transport as a separate projects. However I did not forget that
>> ;-)
>> As the first step I moved all the transport into a separate module
>> into Axis2 called "transports" and add dependency to that module ,
>> for all the module which are going to use Axis2 transport.
>>
>> As I mentioned the moving is not complete , since I think there are
>> some code cleanup has to be done before moving into a separate
>> project. Once I done with that I will give you the green light.
>>
>> I have make sure that all the test cases are working fine after my
>> changes , but you also run the build and see whether thats works fine
>> for you.
>>> Ah I forgot about the commons-dev aspect. Maybe its easier to avoid
>>> yet another list and use commons-dev .. so I'm fine with what you
>>> proposed.
>>>
>>> Sanjiva.
>>>
>>> Glen Daniels wrote:
>>>> Hey Sanjiva:
>>>>
>>>> Sanjiva Weerawarana wrote:
>>>>> Glen, why ws/commons/transports? Why not ws/transports??
>>>> >
>>
>>
>> --
>> Thanks,
>> Deepal
>> ................................................................
>> http://blogs.deepal.org/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Thanks,
Deepal
................................................................
http://blogs.deepal.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2]WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
Yes I found that and I am working on that now.
> axis2-kernel doesn't build anymore because it depends on classes in
> org.apache.axis2.transport.http.util which are no longer there.
>
> Andreas
>
> On 24 juin 08, at 13:13, Deepal jayasinghe wrote:
>
>> Hi all,
>>
>> I think most of you guys have forgotten about the proposal of moving
>> Axis2 transport as a separate projects. However I did not forget that
>> ;-)
>> As the first step I moved all the transport into a separate module
>> into Axis2 called "transports" and add dependency to that module ,
>> for all the module which are going to use Axis2 transport.
>>
>> As I mentioned the moving is not complete , since I think there are
>> some code cleanup has to be done before moving into a separate
>> project. Once I done with that I will give you the green light.
>>
>> I have make sure that all the test cases are working fine after my
>> changes , but you also run the build and see whether thats works fine
>> for you.
>>> Ah I forgot about the commons-dev aspect. Maybe its easier to avoid
>>> yet another list and use commons-dev .. so I'm fine with what you
>>> proposed.
>>>
>>> Sanjiva.
>>>
>>> Glen Daniels wrote:
>>>> Hey Sanjiva:
>>>>
>>>> Sanjiva Weerawarana wrote:
>>>>> Glen, why ws/commons/transports? Why not ws/transports??
>>>> >
>>
>>
>> --
>> Thanks,
>> Deepal
>> ................................................................
>> http://blogs.deepal.org/
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Thanks,
Deepal
................................................................
http://blogs.deepal.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]WS-Commons transports project
Posted by Andreas Veithen <an...@skynet.be>.
axis2-kernel doesn't build anymore because it depends on classes in
org.apache.axis2.transport.http.util which are no longer there.
Andreas
On 24 juin 08, at 13:13, Deepal jayasinghe wrote:
> Hi all,
>
> I think most of you guys have forgotten about the proposal of moving
> Axis2 transport as a separate projects. However I did not forget
> that ;-)
> As the first step I moved all the transport into a separate module
> into Axis2 called "transports" and add dependency to that module ,
> for all the module which are going to use Axis2 transport.
>
> As I mentioned the moving is not complete , since I think there are
> some code cleanup has to be done before moving into a separate
> project. Once I done with that I will give you the green light.
>
> I have make sure that all the test cases are working fine after my
> changes , but you also run the build and see whether thats works
> fine for you.
>> Ah I forgot about the commons-dev aspect. Maybe its easier to avoid
>> yet another list and use commons-dev .. so I'm fine with what you
>> proposed.
>>
>> Sanjiva.
>>
>> Glen Daniels wrote:
>>> Hey Sanjiva:
>>>
>>> Sanjiva Weerawarana wrote:
>>>> Glen, why ws/commons/transports? Why not ws/transports??
>>> >
>
>
> --
> Thanks,
> Deepal
> ................................................................
> http://blogs.deepal.org/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2]WS-Commons transports project
Posted by Andreas Veithen <an...@skynet.be>.
axis2-kernel doesn't build anymore because it depends on classes in
org.apache.axis2.transport.http.util which are no longer there.
Andreas
On 24 juin 08, at 13:13, Deepal jayasinghe wrote:
> Hi all,
>
> I think most of you guys have forgotten about the proposal of moving
> Axis2 transport as a separate projects. However I did not forget
> that ;-)
> As the first step I moved all the transport into a separate module
> into Axis2 called "transports" and add dependency to that module ,
> for all the module which are going to use Axis2 transport.
>
> As I mentioned the moving is not complete , since I think there are
> some code cleanup has to be done before moving into a separate
> project. Once I done with that I will give you the green light.
>
> I have make sure that all the test cases are working fine after my
> changes , but you also run the build and see whether thats works
> fine for you.
>> Ah I forgot about the commons-dev aspect. Maybe its easier to avoid
>> yet another list and use commons-dev .. so I'm fine with what you
>> proposed.
>>
>> Sanjiva.
>>
>> Glen Daniels wrote:
>>> Hey Sanjiva:
>>>
>>> Sanjiva Weerawarana wrote:
>>>> Glen, why ws/commons/transports? Why not ws/transports??
>>> >
>
>
> --
> Thanks,
> Deepal
> ................................................................
> http://blogs.deepal.org/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2]WS-Commons transports project
Posted by Andreas Veithen <an...@skynet.be>.
On June 24, at 13:13, Deepal jayasinghe wrote:
> I think most of you guys have forgotten about the proposal of moving
> Axis2 transport as a separate projects. However I did not forget
> that ;-)
You did (well, almost ;-)
More seriously, now that you are going to move the existing Axis2
transports to the ws-commons project, it will be our turn to move the
Synapse transports there. Did anybody start to elaborate a plan to do
this? I think there are several steps that must be completed before we
can do this move.
Regards,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2]WS-Commons transports project
Posted by Andreas Veithen <an...@skynet.be>.
On June 24, at 13:13, Deepal jayasinghe wrote:
> I think most of you guys have forgotten about the proposal of moving
> Axis2 transport as a separate projects. However I did not forget
> that ;-)
You did (well, almost ;-)
More seriously, now that you are going to move the existing Axis2
transports to the ws-commons project, it will be our turn to move the
Synapse transports there. Did anybody start to elaborate a plan to do
this? I think there are several steps that must be completed before we
can do this move.
Regards,
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[Axis2]WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
Hi all,
I think most of you guys have forgotten about the proposal of moving
Axis2 transport as a separate projects. However I did not forget that ;-)
As the first step I moved all the transport into a separate module into
Axis2 called "transports" and add dependency to that module , for all
the module which are going to use Axis2 transport.
As I mentioned the moving is not complete , since I think there are some
code cleanup has to be done before moving into a separate project. Once
I done with that I will give you the green light.
I have make sure that all the test cases are working fine after my
changes , but you also run the build and see whether thats works fine
for you.
> Ah I forgot about the commons-dev aspect. Maybe its easier to avoid
> yet another list and use commons-dev .. so I'm fine with what you
> proposed.
>
> Sanjiva.
>
> Glen Daniels wrote:
>> Hey Sanjiva:
>>
>> Sanjiva Weerawarana wrote:
>>> Glen, why ws/commons/transports? Why not ws/transports??
>> >
--
Thanks,
Deepal
................................................................
http://blogs.deepal.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[Axis2]WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
Hi all,
I think most of you guys have forgotten about the proposal of moving
Axis2 transport as a separate projects. However I did not forget that ;-)
As the first step I moved all the transport into a separate module into
Axis2 called "transports" and add dependency to that module , for all
the module which are going to use Axis2 transport.
As I mentioned the moving is not complete , since I think there are some
code cleanup has to be done before moving into a separate project. Once
I done with that I will give you the green light.
I have make sure that all the test cases are working fine after my
changes , but you also run the build and see whether thats works fine
for you.
> Ah I forgot about the commons-dev aspect. Maybe its easier to avoid
> yet another list and use commons-dev .. so I'm fine with what you
> proposed.
>
> Sanjiva.
>
> Glen Daniels wrote:
>> Hey Sanjiva:
>>
>> Sanjiva Weerawarana wrote:
>>> Glen, why ws/commons/transports? Why not ws/transports??
>> >
--
Thanks,
Deepal
................................................................
http://blogs.deepal.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Ah I forgot about the commons-dev aspect. Maybe its easier to avoid yet
another list and use commons-dev .. so I'm fine with what you proposed.
Sanjiva.
Glen Daniels wrote:
> Hey Sanjiva:
>
> Sanjiva Weerawarana wrote:
>> Glen, why ws/commons/transports? Why not ws/transports??
> >
>> We've moved away from commons in Axiom etc. - that is, packages no
>> longer say that and IMO that's better.
>
> The package names don't matter - I'm talking about organization of the
> project. Axiom, Neethi, etc. are all under webservices/commons in SVN,
> and they all use commons-dev for discussion. Since commons is a place
> to put common components that are used across the WS universe (and
> elsewhere), that made sense to me as a place to put transports.
>
> I'm fine with webservices/transports too, although I still think they
> would actually make the most sense as separately buildable/deployable
> artifacts under axis2/.
>
> If we're all in agreement for webservices/transports, let's do that, and
> I guess we should kick off transports-dev@ws.apache.org too.
>
> --Glen
>
>> Deepal jayasinghe wrote:
>>> Glen Daniels wrote:
>>>> [ Please refer to this thread for context :
>>>> http://markmail.org/message/lg3giq5kj74gjnxb
>>>> ]
>>>>
>>>>
>>>> OK, let me make a concrete proposal here.
>>>>
>>>> I hereby propose that we kick off a ws-commons "transports"
>>>> project. As with the other ws-commons projects, this would have its
>>>> own release schedule. All current ws-all committers would have
>>>> commit rights, and we'd add anyone from the Synapse team that would
>>>> like to work on transports, and isn't already a committer.
>>> +1 for making a commons project for Axis2 transports. This will help
>>> both Axis2 and other dependent projects such as Synapse.
>>>>
>>>> Each transport within ws-commons Transports would be a separate
>>>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>>>> each such transport would be releasable on its own with an
>>>> appropriate VOTE of the ws-commons committers.
>>> Personally I would like to download all the transport as a single jar
>>> , but I do not mind releasing them separately as long as you give
>>> single jar as well.
>>>
>>> Thank you!
>>> Deepal
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Deepal Jayasinghe <de...@opensource.lk>.
> Hey Sanjiva:
>
> Sanjiva Weerawarana wrote:
>> Glen, why ws/commons/transports? Why not ws/transports??
> >
>> We've moved away from commons in Axiom etc. - that is, packages no
>> longer say that and IMO that's better.
>
> The package names don't matter - I'm talking about organization of the
> project. Axiom, Neethi, etc. are all under webservices/commons in
> SVN, and they all use commons-dev for discussion. Since commons is a
> place to put common components that are used across the WS universe
> (and elsewhere), that made sense to me as a place to put transports.
+1
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Ah I forgot about the commons-dev aspect. Maybe its easier to avoid yet
another list and use commons-dev .. so I'm fine with what you proposed.
Sanjiva.
Glen Daniels wrote:
> Hey Sanjiva:
>
> Sanjiva Weerawarana wrote:
>> Glen, why ws/commons/transports? Why not ws/transports??
> >
>> We've moved away from commons in Axiom etc. - that is, packages no
>> longer say that and IMO that's better.
>
> The package names don't matter - I'm talking about organization of the
> project. Axiom, Neethi, etc. are all under webservices/commons in SVN,
> and they all use commons-dev for discussion. Since commons is a place
> to put common components that are used across the WS universe (and
> elsewhere), that made sense to me as a place to put transports.
>
> I'm fine with webservices/transports too, although I still think they
> would actually make the most sense as separately buildable/deployable
> artifacts under axis2/.
>
> If we're all in agreement for webservices/transports, let's do that, and
> I guess we should kick off transports-dev@ws.apache.org too.
>
> --Glen
>
>> Deepal jayasinghe wrote:
>>> Glen Daniels wrote:
>>>> [ Please refer to this thread for context :
>>>> http://markmail.org/message/lg3giq5kj74gjnxb
>>>> ]
>>>>
>>>>
>>>> OK, let me make a concrete proposal here.
>>>>
>>>> I hereby propose that we kick off a ws-commons "transports"
>>>> project. As with the other ws-commons projects, this would have its
>>>> own release schedule. All current ws-all committers would have
>>>> commit rights, and we'd add anyone from the Synapse team that would
>>>> like to work on transports, and isn't already a committer.
>>> +1 for making a commons project for Axis2 transports. This will help
>>> both Axis2 and other dependent projects such as Synapse.
>>>>
>>>> Each transport within ws-commons Transports would be a separate
>>>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>>>> each such transport would be releasable on its own with an
>>>> appropriate VOTE of the ws-commons committers.
>>> Personally I would like to download all the transport as a single jar
>>> , but I do not mind releasing them separately as long as you give
>>> single jar as well.
>>>
>>> Thank you!
>>> Deepal
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>>> For additional commands, e-mail: dev-help@synapse.apache.org
>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hey Sanjiva:
Sanjiva Weerawarana wrote:
> Glen, why ws/commons/transports? Why not ws/transports??
>
> We've moved away from commons in Axiom etc. - that is, packages no
> longer say that and IMO that's better.
The package names don't matter - I'm talking about organization of the
project. Axiom, Neethi, etc. are all under webservices/commons in SVN,
and they all use commons-dev for discussion. Since commons is a place
to put common components that are used across the WS universe (and
elsewhere), that made sense to me as a place to put transports.
I'm fine with webservices/transports too, although I still think they
would actually make the most sense as separately buildable/deployable
artifacts under axis2/.
If we're all in agreement for webservices/transports, let's do that, and
I guess we should kick off transports-dev@ws.apache.org too.
--Glen
> Deepal jayasinghe wrote:
>> Glen Daniels wrote:
>>> [ Please refer to this thread for context :
>>> http://markmail.org/message/lg3giq5kj74gjnxb
>>> ]
>>>
>>>
>>> OK, let me make a concrete proposal here.
>>>
>>> I hereby propose that we kick off a ws-commons "transports" project.
>>> As with the other ws-commons projects, this would have its own
>>> release schedule. All current ws-all committers would have commit
>>> rights, and we'd add anyone from the Synapse team that would like to
>>> work on transports, and isn't already a committer.
>> +1 for making a commons project for Axis2 transports. This will help
>> both Axis2 and other dependent projects such as Synapse.
>>>
>>> Each transport within ws-commons Transports would be a separate
>>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>>> each such transport would be releasable on its own with an
>>> appropriate VOTE of the ws-commons committers.
>> Personally I would like to download all the transport as a single jar
>> , but I do not mind releasing them separately as long as you give
>> single jar as well.
>>
>> Thank you!
>> Deepal
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Hey Sanjiva:
Sanjiva Weerawarana wrote:
> Glen, why ws/commons/transports? Why not ws/transports??
>
> We've moved away from commons in Axiom etc. - that is, packages no
> longer say that and IMO that's better.
The package names don't matter - I'm talking about organization of the
project. Axiom, Neethi, etc. are all under webservices/commons in SVN,
and they all use commons-dev for discussion. Since commons is a place
to put common components that are used across the WS universe (and
elsewhere), that made sense to me as a place to put transports.
I'm fine with webservices/transports too, although I still think they
would actually make the most sense as separately buildable/deployable
artifacts under axis2/.
If we're all in agreement for webservices/transports, let's do that, and
I guess we should kick off transports-dev@ws.apache.org too.
--Glen
> Deepal jayasinghe wrote:
>> Glen Daniels wrote:
>>> [ Please refer to this thread for context :
>>> http://markmail.org/message/lg3giq5kj74gjnxb
>>> ]
>>>
>>>
>>> OK, let me make a concrete proposal here.
>>>
>>> I hereby propose that we kick off a ws-commons "transports" project.
>>> As with the other ws-commons projects, this would have its own
>>> release schedule. All current ws-all committers would have commit
>>> rights, and we'd add anyone from the Synapse team that would like to
>>> work on transports, and isn't already a committer.
>> +1 for making a commons project for Axis2 transports. This will help
>> both Axis2 and other dependent projects such as Synapse.
>>>
>>> Each transport within ws-commons Transports would be a separate
>>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>>> each such transport would be releasable on its own with an
>>> appropriate VOTE of the ws-commons committers.
>> Personally I would like to download all the transport as a single jar
>> , but I do not mind releasing them separately as long as you give
>> single jar as well.
>>
>> Thank you!
>> Deepal
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
> Glen, why ws/commons/transports? Why not ws/transports??
Even though we call ws/commons/transports or ws/transports those
components only valid for Axis2. Therefore I can not see the value of
having axis2 transport under WS [ I know I did +1 on the proposal.] :-\
>
> We've moved away from commons in Axiom etc. - that is, packages no
> longer say that and IMO that's better.
Yes. If we are moving the transport to ws , then it should not be inside
ws/commons , should be just ws/transport. But one thing we need to keep
in mind , we should not change the package name. If we do so we loose
the backward compatibility again.
With all these I think the time has come to think of moving Axis2 as TLP :)
Thank you!
Deepl
>
> Sanjiva.
>
> Deepal jayasinghe wrote:
>> Glen Daniels wrote:
>>> [ Please refer to this thread for context :
>>> http://markmail.org/message/lg3giq5kj74gjnxb
>>> ]
>>>
>>>
>>> OK, let me make a concrete proposal here.
>>>
>>> I hereby propose that we kick off a ws-commons "transports"
>>> project. As with the other ws-commons projects, this would have its
>>> own release schedule. All current ws-all committers would have
>>> commit rights, and we'd add anyone from the Synapse team that would
>>> like to work on transports, and isn't already a committer.
>> +1 for making a commons project for Axis2 transports. This will help
>> both Axis2 and other dependent projects such as Synapse.
>>>
>>> Each transport within ws-commons Transports would be a separate
>>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>>> each such transport would be releasable on its own with an
>>> appropriate VOTE of the ws-commons committers.
>> Personally I would like to download all the transport as a single jar
>> , but I do not mind releasing them separately as long as you give
>> single jar as well.
>>
>> Thank you!
>> Deepal
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Samisa Abeysinghe <sa...@wso2.com>.
Sanjiva Weerawarana wrote:
> Glen, why ws/commons/transports? Why not ws/transports??
+1. And mid you, there will be Java transports as well as C transports.
Count Axis2/C as well.
Samisa...
>
> We've moved away from commons in Axiom etc. - that is, packages no
> longer say that and IMO that's better.
>
> Sanjiva.
>
> Deepal jayasinghe wrote:
>> Glen Daniels wrote:
>>> [ Please refer to this thread for context :
>>> http://markmail.org/message/lg3giq5kj74gjnxb
>>> ]
>>>
>>>
>>> OK, let me make a concrete proposal here.
>>>
>>> I hereby propose that we kick off a ws-commons "transports"
>>> project. As with the other ws-commons projects, this would have its
>>> own release schedule. All current ws-all committers would have
>>> commit rights, and we'd add anyone from the Synapse team that would
>>> like to work on transports, and isn't already a committer.
>> +1 for making a commons project for Axis2 transports. This will help
>> both Axis2 and other dependent projects such as Synapse.
>>>
>>> Each transport within ws-commons Transports would be a separate
>>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>>> each such transport would be releasable on its own with an
>>> appropriate VOTE of the ws-commons committers.
>> Personally I would like to download all the transport as a single jar
>> , but I do not mind releasing them separately as long as you give
>> single jar as well.
>>
>> Thank you!
>> Deepal
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>>
>>
>
--
Samisa Abeysinghe
Director, Engineering; WSO2 Inc.
http://www.wso2.com/ - "The Open Source SOA Company"
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Glen, why ws/commons/transports? Why not ws/transports??
We've moved away from commons in Axiom etc. - that is, packages no longer
say that and IMO that's better.
Sanjiva.
Deepal jayasinghe wrote:
> Glen Daniels wrote:
>> [ Please refer to this thread for context :
>> http://markmail.org/message/lg3giq5kj74gjnxb
>> ]
>>
>>
>> OK, let me make a concrete proposal here.
>>
>> I hereby propose that we kick off a ws-commons "transports" project.
>> As with the other ws-commons projects, this would have its own release
>> schedule. All current ws-all committers would have commit rights, and
>> we'd add anyone from the Synapse team that would like to work on
>> transports, and isn't already a committer.
> +1 for making a commons project for Axis2 transports. This will help
> both Axis2 and other dependent projects such as Synapse.
>>
>> Each transport within ws-commons Transports would be a separate
>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>> each such transport would be releasable on its own with an appropriate
>> VOTE of the ws-commons committers.
> Personally I would like to download all the transport as a single jar ,
> but I do not mind releasing them separately as long as you give single
> jar as well.
>
> Thank you!
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
Glen, why ws/commons/transports? Why not ws/transports??
We've moved away from commons in Axiom etc. - that is, packages no longer
say that and IMO that's better.
Sanjiva.
Deepal jayasinghe wrote:
> Glen Daniels wrote:
>> [ Please refer to this thread for context :
>> http://markmail.org/message/lg3giq5kj74gjnxb
>> ]
>>
>>
>> OK, let me make a concrete proposal here.
>>
>> I hereby propose that we kick off a ws-commons "transports" project.
>> As with the other ws-commons projects, this would have its own release
>> schedule. All current ws-all committers would have commit rights, and
>> we'd add anyone from the Synapse team that would like to work on
>> transports, and isn't already a committer.
> +1 for making a commons project for Axis2 transports. This will help
> both Axis2 and other dependent projects such as Synapse.
>>
>> Each transport within ws-commons Transports would be a separate
>> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
>> each such transport would be releasable on its own with an appropriate
>> VOTE of the ws-commons committers.
> Personally I would like to download all the transport as a single jar ,
> but I do not mind releasing them separately as long as you give single
> jar as well.
>
> Thank you!
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
Glen Daniels wrote:
> [ Please refer to this thread for context :
> http://markmail.org/message/lg3giq5kj74gjnxb
> ]
>
>
> OK, let me make a concrete proposal here.
>
> I hereby propose that we kick off a ws-commons "transports" project.
> As with the other ws-commons projects, this would have its own release
> schedule. All current ws-all committers would have commit rights, and
> we'd add anyone from the Synapse team that would like to work on
> transports, and isn't already a committer.
+1 for making a commons project for Axis2 transports. This will help
both Axis2 and other dependent projects such as Synapse.
>
> Each transport within ws-commons Transports would be a separate
> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
> each such transport would be releasable on its own with an appropriate
> VOTE of the ws-commons committers.
Personally I would like to download all the transport as a single jar ,
but I do not mind releasing them separately as long as you give single
jar as well.
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Afkham Azeez <af...@gmail.com>.
+1
Azeez
On Wed, Apr 23, 2008 at 2:12 AM, Glen Daniels <gl...@thoughtcraft.com> wrote:
> [ Please refer to this thread for context :
> http://markmail.org/message/lg3giq5kj74gjnxb
> ]
>
>
> OK, let me make a concrete proposal here.
>
> I hereby propose that we kick off a ws-commons "transports" project. As
> with the other ws-commons projects, this would have its own release
> schedule. All current ws-all committers would have commit rights, and we'd
> add anyone from the Synapse team that would like to work on transports, and
> isn't already a committer.
>
> Each transport within ws-commons Transports would be a separate releasable
> artifact, i.e. "org.apache.ws.transports.jms" etc... and each such transport
> would be releasable on its own with an appropriate VOTE of the ws-commons
> committers.
>
> We'd use commons-dev and commons-user mailing lists as per usual for
> communication, and SVN would be
> webservices/commons/trunk/modules/transports.
>
> We'd get started by moving whichever transports in Axis2 and Synapse are
> appropriate into the new source tree.
>
> Here's my +1. Please comment / VOTE at will.
>
> --Glen
>
--
Thanks
Afkham Azeez
http://azeez78.blogspot.com
http://www.wso2.org
GPG Fingerprint: 643F C2AF EB78 F886 40C9 B2A2 4AE2 C887 665E 0760
Re: [VOTE] [Proposal] WS-Commons transports project
Posted by Deepal jayasinghe <de...@gmail.com>.
Glen Daniels wrote:
> [ Please refer to this thread for context :
> http://markmail.org/message/lg3giq5kj74gjnxb
> ]
>
>
> OK, let me make a concrete proposal here.
>
> I hereby propose that we kick off a ws-commons "transports" project.
> As with the other ws-commons projects, this would have its own release
> schedule. All current ws-all committers would have commit rights, and
> we'd add anyone from the Synapse team that would like to work on
> transports, and isn't already a committer.
+1 for making a commons project for Axis2 transports. This will help
both Axis2 and other dependent projects such as Synapse.
>
> Each transport within ws-commons Transports would be a separate
> releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and
> each such transport would be releasable on its own with an appropriate
> VOTE of the ws-commons committers.
Personally I would like to download all the transport as a single jar ,
but I do not mind releasing them separately as long as you give single
jar as well.
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[VOTE] [Proposal] WS-Commons transports project
Posted by Glen Daniels <gl...@thoughtcraft.com>.
[ Please refer to this thread for context :
http://markmail.org/message/lg3giq5kj74gjnxb
]
OK, let me make a concrete proposal here.
I hereby propose that we kick off a ws-commons "transports" project. As
with the other ws-commons projects, this would have its own release
schedule. All current ws-all committers would have commit rights, and
we'd add anyone from the Synapse team that would like to work on
transports, and isn't already a committer.
Each transport within ws-commons Transports would be a separate
releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
such transport would be releasable on its own with an appropriate VOTE
of the ws-commons committers.
We'd use commons-dev and commons-user mailing lists as per usual for
communication, and SVN would be
webservices/commons/trunk/modules/transports.
We'd get started by moving whichever transports in Axis2 and Synapse are
appropriate into the new source tree.
Here's my +1. Please comment / VOTE at will.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
[VOTE] [Proposal] WS-Commons transports project
Posted by Glen Daniels <gl...@thoughtcraft.com>.
[ Please refer to this thread for context :
http://markmail.org/message/lg3giq5kj74gjnxb
]
OK, let me make a concrete proposal here.
I hereby propose that we kick off a ws-commons "transports" project. As
with the other ws-commons projects, this would have its own release
schedule. All current ws-all committers would have commit rights, and
we'd add anyone from the Synapse team that would like to work on
transports, and isn't already a committer.
Each transport within ws-commons Transports would be a separate
releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
such transport would be releasable on its own with an appropriate VOTE
of the ws-commons committers.
We'd use commons-dev and commons-user mailing lists as per usual for
communication, and SVN would be
webservices/commons/trunk/modules/transports.
We'd get started by moving whichever transports in Axis2 and Synapse are
appropriate into the new source tree.
Here's my +1. Please comment / VOTE at will.
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[VOTE] [Proposal] WS-Commons transports project
Posted by Glen Daniels <gl...@thoughtcraft.com>.
[ Please refer to this thread for context :
http://markmail.org/message/lg3giq5kj74gjnxb
]
OK, let me make a concrete proposal here.
I hereby propose that we kick off a ws-commons "transports" project. As
with the other ws-commons projects, this would have its own release
schedule. All current ws-all committers would have commit rights, and
we'd add anyone from the Synapse team that would like to work on
transports, and isn't already a committer.
Each transport within ws-commons Transports would be a separate
releasable artifact, i.e. "org.apache.ws.transports.jms" etc... and each
such transport would be releasable on its own with an appropriate VOTE
of the ws-commons committers.
We'd use commons-dev and commons-user mailing lists as per usual for
communication, and SVN would be
webservices/commons/trunk/modules/transports.
We'd get started by moving whichever transports in Axis2 and Synapse are
appropriate into the new source tree.
Here's my +1. Please comment / VOTE at will.
--Glen
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
David
> Asankha, is there something about doing this work in Axis2 that is
> difficult for you and easily changed e.g. having a separate release
> schedule for the 'extra transports',
One of the main issues here to consider is how easily we can fix issues,
create patches and release versions of the transports when Synapse wants
them.. remember that "we" are the primary users of these transports with
customers using these in production..
First of all, having the code only in axis2 trunk would mean that
sometimes we may not be even able to compile it when required ;-) , or
having to download many many more JARs each time we want to build.. and
also somehow get through the common build breaks! We will also exposed
to all changes taking place on the axis2 trunk, and forced to comply to
keep compatibility at trunk with Axis2. Usually [if not always] Synapse
depends on the last Axis2 released version. For example, we were using
Axis2 1.3 for many months, until we were ready to move to Axis2 1.4
now... and we wanted our transports to remain on Axis2 1.3 until then.
Synapse is very much dependent on transports, esp when it comes to
legacy transports other than http/s. Most of the time we need to make
changes to transports to fix bugs and/or perform enhancements. I also
believe that the NIO http/s transports is one of the most valuable and
complicated pieces of code on which Synapse relies heavily.. I don't
understand the argument that you want to make it easier for a casual
user of Axis2 to use these transports, putting the Synapse team that
develops these and uses these much more, into the "difficult" position?
If anyone wants to use any of the Synapse transports, they:
(1) Do not need to download Synapse
(2) Learn about or know Synapse
(3) Be dependent on the Synapse core JARs
All they need to do is put an entry into the pom.xml of their project to
point to the synapse-transports.jar! Technically this is no different
than a separate module in Axis2, or WS commons.. Of course they will
need to understand how each transport operates (e.g. FIX, VFS etc..)
before trying to use them.. but this is not solved by where the code
lies, but in providing documentation
> or is it more cultural that you're doing all your work in Synapse now?
>
Not at all! ..
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by David Illsley <da...@gmail.com>.
This seems like an inevitable, if unfortunate result of spinning
Synapse off as a separate TLP.
Asankha, is there something about doing this work in Axis2 that is
difficult for you and easily changed e.g. having a separate release
schedule for the 'extra transports', or is it more cultural that
you're doing all your work in Synapse now?
David
On Tue, Apr 22, 2008 at 6:18 PM, Davanum Srinivas <da...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> At this point, Can we please agree that it's better for the people who
> actually work on it have their way :)
>
> thanks,
> dims
>
>
>
> Glen Daniels wrote:
> | Asankha C. Perera wrote:
> |> Dims
> |>> - there should not be stale copies
> |>> - people who work on them should work where they want to.
> |> +1 to both!
> |
> | Agreed - I'd just prefer people wanted to work on them under WS/Axis. :)
> |
> |> I'd like to maintain these under Synapse.. We wrote these transports
> |> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail,
> |> VFS (File), FIX and AMQP already.. These belong to a separate Maven
> |> module thats published to the Apache snapshots and Maven Central
> |> repos, and
> |
> | Hm. So this is a bit of a separate conversation, but *each* of the
> | transports should be its own deployable artifact. If I want the AMQP
> | transport for some work I'm doing, I don't want to bother downloading
> | all the others.... Wherever they end up we should fix that!!
> |
> |> this JAR does not depend on the Synapse codebase at all. Anyone who
> |> wishes to use these can do so without any problems whatsoever, and
> |> raise JIRA's for bugs/enhancements where the code is actually
> maintained.
> |
> | Yeah. I just think this makes a lot more sense under WS.
> |
> |>> | | These transports (JMS, NIO, whatever) are going to be generally
> |>> useful to any Axis2 user, so why make them go look in Synapse's
> |>> codebase for them?
> |> I agree,.. however these transports were written by the Synapse
> |> community for primary use by them. So instead of asking them to
> |> maintain the code they write somewhere else - for the convenience of
> |> the secondary users, why not clearly document the available options
> |> under Axis2 and where one could download these extension transports
> |> developed by the Synapse community?
> |
> | Sure, I'm not saying that wouldn't work - what's really important to me
> | is that Axis2 users get a clear picture of the available transports when
> | they download Axis2 and use our website. This is both to avoid
> | duplication of effort and to enable users to use the richest set of
> | components available. It seems to me that the most natural way to
> | achieve this is to contribute new transports to ws-commons or Axis2.
> |
> | Also consider this - wouldn't it be cool to be able to run the Axis2
> | test suite (which is presumably much more comprehensive than Synapse's
> | testing of Axis2) over each of the transports that Synapse originally
> | built? I would think that might demonstrate some issues that Synapse
> | itself might not find, thus enabling the transports to be improved.
> |
> | But if the community wants to keep developing these under Synapse, then
> | we definitely need some pointers in the Axis2 code and web pages, and
> | those pointers need to be maintained.
> |
> | Thanks,
> | --Glen
> |
> | ---------------------------------------------------------------------
> | To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> | For additional commands, e-mail: axis-dev-help@ws.apache.org
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
> n+u3lNY14rCRKaSFT9s+Hw==
> =Nw0Q
> -----END PGP SIGNATURE-----
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Glen,
At this point, Can we please agree that it's better for the people who actually work on it have their way :)
thanks,
dims
Glen Daniels wrote:
| Asankha C. Perera wrote:
|> Dims
|>> - there should not be stale copies
|>> - people who work on them should work where they want to.
|> +1 to both!
|
| Agreed - I'd just prefer people wanted to work on them under WS/Axis. :)
|
|> I'd like to maintain these under Synapse.. We wrote these transports
|> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail,
|> VFS (File), FIX and AMQP already.. These belong to a separate Maven
|> module thats published to the Apache snapshots and Maven Central
|> repos, and
|
| Hm. So this is a bit of a separate conversation, but *each* of the
| transports should be its own deployable artifact. If I want the AMQP
| transport for some work I'm doing, I don't want to bother downloading
| all the others.... Wherever they end up we should fix that!!
|
|> this JAR does not depend on the Synapse codebase at all. Anyone who
|> wishes to use these can do so without any problems whatsoever, and
|> raise JIRA's for bugs/enhancements where the code is actually maintained.
|
| Yeah. I just think this makes a lot more sense under WS.
|
|>> | | These transports (JMS, NIO, whatever) are going to be generally
|>> useful to any Axis2 user, so why make them go look in Synapse's
|>> codebase for them?
|> I agree,.. however these transports were written by the Synapse
|> community for primary use by them. So instead of asking them to
|> maintain the code they write somewhere else - for the convenience of
|> the secondary users, why not clearly document the available options
|> under Axis2 and where one could download these extension transports
|> developed by the Synapse community?
|
| Sure, I'm not saying that wouldn't work - what's really important to me
| is that Axis2 users get a clear picture of the available transports when
| they download Axis2 and use our website. This is both to avoid
| duplication of effort and to enable users to use the richest set of
| components available. It seems to me that the most natural way to
| achieve this is to contribute new transports to ws-commons or Axis2.
|
| Also consider this - wouldn't it be cool to be able to run the Axis2
| test suite (which is presumably much more comprehensive than Synapse's
| testing of Axis2) over each of the transports that Synapse originally
| built? I would think that might demonstrate some issues that Synapse
| itself might not find, thus enabling the transports to be improved.
|
| But if the community wants to keep developing these under Synapse, then
| we definitely need some pointers in the Axis2 code and web pages, and
| those pointers need to be maintained.
|
| Thanks,
| --Glen
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| For additional commands, e-mail: axis-dev-help@ws.apache.org
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
n+u3lNY14rCRKaSFT9s+Hw==
=Nw0Q
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Glen,
At this point, Can we please agree that it's better for the people who actually work on it have their way :)
thanks,
dims
Glen Daniels wrote:
| Asankha C. Perera wrote:
|> Dims
|>> - there should not be stale copies
|>> - people who work on them should work where they want to.
|> +1 to both!
|
| Agreed - I'd just prefer people wanted to work on them under WS/Axis. :)
|
|> I'd like to maintain these under Synapse.. We wrote these transports
|> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail,
|> VFS (File), FIX and AMQP already.. These belong to a separate Maven
|> module thats published to the Apache snapshots and Maven Central
|> repos, and
|
| Hm. So this is a bit of a separate conversation, but *each* of the
| transports should be its own deployable artifact. If I want the AMQP
| transport for some work I'm doing, I don't want to bother downloading
| all the others.... Wherever they end up we should fix that!!
|
|> this JAR does not depend on the Synapse codebase at all. Anyone who
|> wishes to use these can do so without any problems whatsoever, and
|> raise JIRA's for bugs/enhancements where the code is actually maintained.
|
| Yeah. I just think this makes a lot more sense under WS.
|
|>> | | These transports (JMS, NIO, whatever) are going to be generally
|>> useful to any Axis2 user, so why make them go look in Synapse's
|>> codebase for them?
|> I agree,.. however these transports were written by the Synapse
|> community for primary use by them. So instead of asking them to
|> maintain the code they write somewhere else - for the convenience of
|> the secondary users, why not clearly document the available options
|> under Axis2 and where one could download these extension transports
|> developed by the Synapse community?
|
| Sure, I'm not saying that wouldn't work - what's really important to me
| is that Axis2 users get a clear picture of the available transports when
| they download Axis2 and use our website. This is both to avoid
| duplication of effort and to enable users to use the richest set of
| components available. It seems to me that the most natural way to
| achieve this is to contribute new transports to ws-commons or Axis2.
|
| Also consider this - wouldn't it be cool to be able to run the Axis2
| test suite (which is presumably much more comprehensive than Synapse's
| testing of Axis2) over each of the transports that Synapse originally
| built? I would think that might demonstrate some issues that Synapse
| itself might not find, thus enabling the transports to be improved.
|
| But if the community wants to keep developing these under Synapse, then
| we definitely need some pointers in the Axis2 code and web pages, and
| those pointers need to be maintained.
|
| Thanks,
| --Glen
|
| ---------------------------------------------------------------------
| To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
| For additional commands, e-mail: axis-dev-help@ws.apache.org
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD4DBQFIDh3xgNg6eWEDv1kRArQ9AJ44ct3OR4J4djeY0ttNox3rhpkPGwCXYbdj
n+u3lNY14rCRKaSFT9s+Hw==
=Nw0Q
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Asankha C. Perera wrote:
> Dims
>> - there should not be stale copies
>> - people who work on them should work where they want to.
> +1 to both!
Agreed - I'd just prefer people wanted to work on them under WS/Axis. :)
> I'd like to maintain these under Synapse.. We wrote these transports
> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail, VFS
> (File), FIX and AMQP already.. These belong to a separate Maven module
> thats published to the Apache snapshots and Maven Central repos, and
Hm. So this is a bit of a separate conversation, but *each* of the
transports should be its own deployable artifact. If I want the AMQP
transport for some work I'm doing, I don't want to bother downloading
all the others.... Wherever they end up we should fix that!!
> this JAR does not depend on the Synapse codebase at all. Anyone who
> wishes to use these can do so without any problems whatsoever, and raise
> JIRA's for bugs/enhancements where the code is actually maintained.
Yeah. I just think this makes a lot more sense under WS.
>> | | These transports (JMS, NIO, whatever) are going to be generally
>> useful to any Axis2 user, so why make them go look in Synapse's
>> codebase for them?
> I agree,.. however these transports were written by the Synapse
> community for primary use by them. So instead of asking them to maintain
> the code they write somewhere else - for the convenience of the
> secondary users, why not clearly document the available options under
> Axis2 and where one could download these extension transports developed
> by the Synapse community?
Sure, I'm not saying that wouldn't work - what's really important to me
is that Axis2 users get a clear picture of the available transports when
they download Axis2 and use our website. This is both to avoid
duplication of effort and to enable users to use the richest set of
components available. It seems to me that the most natural way to
achieve this is to contribute new transports to ws-commons or Axis2.
Also consider this - wouldn't it be cool to be able to run the Axis2
test suite (which is presumably much more comprehensive than Synapse's
testing of Axis2) over each of the transports that Synapse originally
built? I would think that might demonstrate some issues that Synapse
itself might not find, thus enabling the transports to be improved.
But if the community wants to keep developing these under Synapse, then
we definitely need some pointers in the Axis2 code and web pages, and
those pointers need to be maintained.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Asankha C. Perera wrote:
> Dims
>> - there should not be stale copies
>> - people who work on them should work where they want to.
> +1 to both!
Agreed - I'd just prefer people wanted to work on them under WS/Axis. :)
> I'd like to maintain these under Synapse.. We wrote these transports
> primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail, VFS
> (File), FIX and AMQP already.. These belong to a separate Maven module
> thats published to the Apache snapshots and Maven Central repos, and
Hm. So this is a bit of a separate conversation, but *each* of the
transports should be its own deployable artifact. If I want the AMQP
transport for some work I'm doing, I don't want to bother downloading
all the others.... Wherever they end up we should fix that!!
> this JAR does not depend on the Synapse codebase at all. Anyone who
> wishes to use these can do so without any problems whatsoever, and raise
> JIRA's for bugs/enhancements where the code is actually maintained.
Yeah. I just think this makes a lot more sense under WS.
>> | | These transports (JMS, NIO, whatever) are going to be generally
>> useful to any Axis2 user, so why make them go look in Synapse's
>> codebase for them?
> I agree,.. however these transports were written by the Synapse
> community for primary use by them. So instead of asking them to maintain
> the code they write somewhere else - for the convenience of the
> secondary users, why not clearly document the available options under
> Axis2 and where one could download these extension transports developed
> by the Synapse community?
Sure, I'm not saying that wouldn't work - what's really important to me
is that Axis2 users get a clear picture of the available transports when
they download Axis2 and use our website. This is both to avoid
duplication of effort and to enable users to use the richest set of
components available. It seems to me that the most natural way to
achieve this is to contribute new transports to ws-commons or Axis2.
Also consider this - wouldn't it be cool to be able to run the Axis2
test suite (which is presumably much more comprehensive than Synapse's
testing of Axis2) over each of the transports that Synapse originally
built? I would think that might demonstrate some issues that Synapse
itself might not find, thus enabling the transports to be improved.
But if the community wants to keep developing these under Synapse, then
we definitely need some pointers in the Axis2 code and web pages, and
those pointers need to be maintained.
Thanks,
--Glen
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Dims
> - there should not be stale copies
> - people who work on them should work where they want to.
+1 to both!
> Right now it's Asankha and co. So we should just make Status Quo
> permanent. It can be under Axis2 as a maven module or
> under WS-Commons or maven module under synapse. I really don't care,
> as long as people who maintain it make the decision
> and do it in one spot.
I'd like to maintain these under Synapse.. We wrote these transports
primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail, VFS
(File), FIX and AMQP already.. These belong to a separate Maven module
thats published to the Apache snapshots and Maven Central repos, and
this JAR does not depend on the Synapse codebase at all. Anyone who
wishes to use these can do so without any problems whatsoever, and raise
JIRA's for bugs/enhancements where the code is actually maintained.
Glen
> | | -1 from me to move them to Synapse.
The transports JMS, NIO-HTTP/S and others are already [developed and
maintained] within Synapse..
> | | These transports (JMS, NIO, whatever) are going to be generally
> useful to any Axis2 user, so why make them go look in Synapse's
> codebase for them?
I agree,.. however these transports were written by the Synapse
community for primary use by them. So instead of asking them to maintain
the code they write somewhere else - for the convenience of the
secondary users, why not clearly document the available options under
Axis2 and where one could download these extension transports developed
by the Synapse community?
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by "Asankha C. Perera" <as...@wso2.com>.
Dims
> - there should not be stale copies
> - people who work on them should work where they want to.
+1 to both!
> Right now it's Asankha and co. So we should just make Status Quo
> permanent. It can be under Axis2 as a maven module or
> under WS-Commons or maven module under synapse. I really don't care,
> as long as people who maintain it make the decision
> and do it in one spot.
I'd like to maintain these under Synapse.. We wrote these transports
primarily for use by Synapse, and now we have JMS, NIO-HTTP/S, Mail, VFS
(File), FIX and AMQP already.. These belong to a separate Maven module
thats published to the Apache snapshots and Maven Central repos, and
this JAR does not depend on the Synapse codebase at all. Anyone who
wishes to use these can do so without any problems whatsoever, and raise
JIRA's for bugs/enhancements where the code is actually maintained.
Glen
> | | -1 from me to move them to Synapse.
The transports JMS, NIO-HTTP/S and others are already [developed and
maintained] within Synapse..
> | | These transports (JMS, NIO, whatever) are going to be generally
> useful to any Axis2 user, so why make them go look in Synapse's
> codebase for them?
I agree,.. however these transports were written by the Synapse
community for primary use by them. So instead of asking them to maintain
the code they write somewhere else - for the convenience of the
secondary users, why not clearly document the available options under
Axis2 and where one could download these extension transports developed
by the Synapse community?
asankha
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michele,
2 thoughts.
- - there should not be stale copies
- - people who work on them should work where they want to.
Right now it's Asankha and co. So we should just make Status Quo permanent. It can be under Axis2 as a maven module or
under WS-Commons or maven module under synapse. I really don't care, as long as people who maintain it make the decision
and do it in one spot.
- -- dims
Michele Mazzucco wrote:
| Dims,
|
| a separate module would probably be better then.
|
|
| Michele
|
|
| On 22 Apr 2008, at 14:29, Davanum Srinivas wrote:
|
| Glen,
|
| If it is not maintained in Axis2, there's absolutely no point keeping
| it here. Right?
|
| -- dims
|
| Glen Daniels wrote:
| | -1 from me to move them to Synapse.
| |
| | These transports (JMS, NIO, whatever) are going to be generally useful
| | to any Axis2 user, so why make them go look in Synapse's codebase for
| | them? I agree there should be a single place for them, but that place
| | should be in Axis2, not somewhere else.
| |
| | I'd much rather see a separate transports module in Axis2 for the ones
| | we want to support (this has been discussed before), and perhaps a
| | "contrib" module to hold transports that others might develop in the
| | future.
| |
| | --Glen
| |
| | Davanum Srinivas wrote:
| | Under synapse...Sure. Perfect.
| |
| | -- dims
| |
| | Paul Fremantle wrote:
| | | I agree there isn't any point keeping stale copies in Axis2. What
| | | about building a separate module or even commons-transports?
| | |
| | | Paul
| | |
| | | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
| | <da...@gmail.com> wrote:
| | |> -----BEGIN PGP SIGNED MESSAGE-----
| | |> Hash: SHA1
| | |>
| | |> Folks,
| | |>
| | |> Let's move JMS and Async NIO transports out of Axis2 into Synapse.
| | There's
| | |> no point keeping a stale copy in Axis2.
| | |>
| | |> WDYT?
| | |>
| | |> Thanks,
| | |> dims
| | |>
|
| |>
| ---------------------------------------------------------------------
| 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
|
|>
- ---------------------------------------------------------------------
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDez4gNg6eWEDv1kRAov6AKCPWLbvTEOsuGM88Z1nPjMuDOU1+wCg2RI3
Ztd6qtUGXHcya6FOemDYFZ8=
=I5p8
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
Dims,
a separate module would probably be better then.
Michele
On 22 Apr 2008, at 14:29, Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> If it is not maintained in Axis2, there's absolutely no point
> keeping it here. Right?
>
> - -- dims
>
> Glen Daniels wrote:
> | -1 from me to move them to Synapse.
> |
> | These transports (JMS, NIO, whatever) are going to be generally
> useful
> | to any Axis2 user, so why make them go look in Synapse's codebase
> for
> | them? I agree there should be a single place for them, but that
> place
> | should be in Axis2, not somewhere else.
> |
> | I'd much rather see a separate transports module in Axis2 for the
> ones
> | we want to support (this has been discussed before), and perhaps a
> | "contrib" module to hold transports that others might develop in the
> | future.
> |
> | --Glen
> |
> | Davanum Srinivas wrote:
> | Under synapse...Sure. Perfect.
> |
> | -- dims
> |
> | Paul Fremantle wrote:
> | | I agree there isn't any point keeping stale copies in Axis2. What
> | | about building a separate module or even commons-transports?
> | |
> | | Paul
> | |
> | | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
> | <da...@gmail.com> wrote:
> | |> -----BEGIN PGP SIGNED MESSAGE-----
> | |> Hash: SHA1
> | |>
> | |> Folks,
> | |>
> | |> Let's move JMS and Async NIO transports out of Axis2 into
> Synapse.
> | There's
> | |> no point keeping a stale copy in Axis2.
> | |>
> | |> WDYT?
> | |>
> | |> Thanks,
> | |> dims
> | |>
>
> |>
> -
> ---------------------------------------------------------------------
> 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDeg6gNg6eWEDv1kRAgTJAJ4pgrpoqNTuP1UdoeOBERFC33X5nwCfR4OX
> bYHHcJchZyt/zGeZgRhgpfE=
> =JxHH
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Let me rephrase succinctly. :)
There should be a single place where generally applicable Axis2
transports get stored. It's fine for other projects to work on
transports, but the ideal situation is for those transports (assuming
they're generic enough) to migrate into the WS PMC as their final
destination, and be developed there.
So I'd like to see the transports in Synapse move into either:
ws-commons/transports/
or
axis2/transports/
And have development and testing continue there. As you say, dims,
there should never be stale code sitting anywhere.
Thoughts?
--Glen
Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> If it is not maintained in Axis2, there's absolutely no point keeping it
> here. Right?
>
> - -- dims
>
> Glen Daniels wrote:
> | -1 from me to move them to Synapse.
> |
> | These transports (JMS, NIO, whatever) are going to be generally useful
> | to any Axis2 user, so why make them go look in Synapse's codebase for
> | them? I agree there should be a single place for them, but that place
> | should be in Axis2, not somewhere else.
> |
> | I'd much rather see a separate transports module in Axis2 for the ones
> | we want to support (this has been discussed before), and perhaps a
> | "contrib" module to hold transports that others might develop in the
> | future.
> |
> | --Glen
> |
> | Davanum Srinivas wrote:
> | Under synapse...Sure. Perfect.
> |
> | -- dims
> |
> | Paul Fremantle wrote:
> | | I agree there isn't any point keeping stale copies in Axis2. What
> | | about building a separate module or even commons-transports?
> | |
> | | Paul
> | |
> | | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
> | <da...@gmail.com> wrote:
> | |> -----BEGIN PGP SIGNED MESSAGE-----
> | |> Hash: SHA1
> | |>
> | |> Folks,
> | |>
> | |> Let's move JMS and Async NIO transports out of Axis2 into Synapse.
> | There's
> | |> no point keeping a stale copy in Axis2.
> | |>
> | |> WDYT?
> | |>
> | |> Thanks,
> | |> dims
> | |>
>
> |>
> - ---------------------------------------------------------------------
> 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDeg6gNg6eWEDv1kRAgTJAJ4pgrpoqNTuP1UdoeOBERFC33X5nwCfR4OX
> bYHHcJchZyt/zGeZgRhgpfE=
> =JxHH
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
Let me rephrase succinctly. :)
There should be a single place where generally applicable Axis2
transports get stored. It's fine for other projects to work on
transports, but the ideal situation is for those transports (assuming
they're generic enough) to migrate into the WS PMC as their final
destination, and be developed there.
So I'd like to see the transports in Synapse move into either:
ws-commons/transports/
or
axis2/transports/
And have development and testing continue there. As you say, dims,
there should never be stale code sitting anywhere.
Thoughts?
--Glen
Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Glen,
>
> If it is not maintained in Axis2, there's absolutely no point keeping it
> here. Right?
>
> - -- dims
>
> Glen Daniels wrote:
> | -1 from me to move them to Synapse.
> |
> | These transports (JMS, NIO, whatever) are going to be generally useful
> | to any Axis2 user, so why make them go look in Synapse's codebase for
> | them? I agree there should be a single place for them, but that place
> | should be in Axis2, not somewhere else.
> |
> | I'd much rather see a separate transports module in Axis2 for the ones
> | we want to support (this has been discussed before), and perhaps a
> | "contrib" module to hold transports that others might develop in the
> | future.
> |
> | --Glen
> |
> | Davanum Srinivas wrote:
> | Under synapse...Sure. Perfect.
> |
> | -- dims
> |
> | Paul Fremantle wrote:
> | | I agree there isn't any point keeping stale copies in Axis2. What
> | | about building a separate module or even commons-transports?
> | |
> | | Paul
> | |
> | | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
> | <da...@gmail.com> wrote:
> | |> -----BEGIN PGP SIGNED MESSAGE-----
> | |> Hash: SHA1
> | |>
> | |> Folks,
> | |>
> | |> Let's move JMS and Async NIO transports out of Axis2 into Synapse.
> | There's
> | |> no point keeping a stale copy in Axis2.
> | |>
> | |> WDYT?
> | |>
> | |> Thanks,
> | |> dims
> | |>
>
> |>
> - ---------------------------------------------------------------------
> 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
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDeg6gNg6eWEDv1kRAgTJAJ4pgrpoqNTuP1UdoeOBERFC33X5nwCfR4OX
> bYHHcJchZyt/zGeZgRhgpfE=
> =JxHH
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> 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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Deepal jayasinghe <de...@gmail.com>.
> Glen,
>
> If it is not maintained in Axis2, there's absolutely no point keeping
> it here. Right?
Well people who maintain the transport in Synapse will also help to
maintain the transport there in Axis2 :)
Thanks
Deepal.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Glen,
If it is not maintained in Axis2, there's absolutely no point keeping it here. Right?
- -- dims
Glen Daniels wrote:
| -1 from me to move them to Synapse.
|
| These transports (JMS, NIO, whatever) are going to be generally useful
| to any Axis2 user, so why make them go look in Synapse's codebase for
| them? I agree there should be a single place for them, but that place
| should be in Axis2, not somewhere else.
|
| I'd much rather see a separate transports module in Axis2 for the ones
| we want to support (this has been discussed before), and perhaps a
| "contrib" module to hold transports that others might develop in the
| future.
|
| --Glen
|
| Davanum Srinivas wrote:
| Under synapse...Sure. Perfect.
|
| -- dims
|
| Paul Fremantle wrote:
| | I agree there isn't any point keeping stale copies in Axis2. What
| | about building a separate module or even commons-transports?
| |
| | Paul
| |
| | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
| <da...@gmail.com> wrote:
| |> -----BEGIN PGP SIGNED MESSAGE-----
| |> Hash: SHA1
| |>
| |> Folks,
| |>
| |> Let's move JMS and Async NIO transports out of Axis2 into Synapse.
| There's
| |> no point keeping a stale copy in Axis2.
| |>
| |> WDYT?
| |>
| |> Thanks,
| |> dims
| |>
|>
- ---------------------------------------------------------------------
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDeg6gNg6eWEDv1kRAgTJAJ4pgrpoqNTuP1UdoeOBERFC33X5nwCfR4OX
bYHHcJchZyt/zGeZgRhgpfE=
=JxHH
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Glen Daniels <gl...@thoughtcraft.com>.
-1 from me to move them to Synapse.
These transports (JMS, NIO, whatever) are going to be generally useful
to any Axis2 user, so why make them go look in Synapse's codebase for
them? I agree there should be a single place for them, but that place
should be in Axis2, not somewhere else.
I'd much rather see a separate transports module in Axis2 for the ones
we want to support (this has been discussed before), and perhaps a
"contrib" module to hold transports that others might develop in the future.
--Glen
Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Under synapse...Sure. Perfect.
>
> - -- dims
>
> Paul Fremantle wrote:
> | I agree there isn't any point keeping stale copies in Axis2. What
> | about building a separate module or even commons-transports?
> |
> | Paul
> |
> | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas <da...@gmail.com>
> wrote:
> |> -----BEGIN PGP SIGNED MESSAGE-----
> |> Hash: SHA1
> |>
> |> Folks,
> |>
> |> Let's move JMS and Async NIO transports out of Axis2 into Synapse.
> There's
> |> no point keeping a stale copy in Axis2.
> |>
> |> WDYT?
> |>
> |> Thanks,
> |> dims
> |> -----BEGIN PGP SIGNATURE-----
> |> Version: GnuPG v1.4.5 (Cygwin)
> |>
> |> iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
> |> nJ5rX+dn2iaC7Fs9/+C+1LE=
> |> =/TIB
> |> -----END PGP SIGNATURE-----
> |>
> |> ---------------------------------------------------------------------
> |> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> |> For additional commands, e-mail: axis-dev-help@ws.apache.org
> |>
> |>
> |
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDdwMgNg6eWEDv1kRAjPdAJ0TdqwjsTLvziHNa/9qC3z8HEkNfgCfQoZl
> qTBtDY480X1XTokdxoojlEg=
> =puTP
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Michele Mazzucco <Mi...@ncl.ac.uk>.
+1 for me.
Michele
On 22 Apr 2008, at 13:37, Davanum Srinivas wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Under synapse...Sure. Perfect.
>
> - -- dims
>
> Paul Fremantle wrote:
> | I agree there isn't any point keeping stale copies in Axis2. What
> | about building a separate module or even commons-transports?
> |
> | Paul
> |
> | On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas
> <da...@gmail.com> wrote:
> |> -----BEGIN PGP SIGNED MESSAGE-----
> |> Hash: SHA1
> |>
> |> Folks,
> |>
> |> Let's move JMS and Async NIO transports out of Axis2 into
> Synapse. There's
> |> no point keeping a stale copy in Axis2.
> |>
> |> WDYT?
> |>
> |> Thanks,
> |> dims
> |> -----BEGIN PGP SIGNATURE-----
> |> Version: GnuPG v1.4.5 (Cygwin)
> |>
> |> iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
> |> nJ5rX+dn2iaC7Fs9/+C+1LE=
> |> =/TIB
> |> -----END PGP SIGNATURE-----
> |>
> |>
> ---------------------------------------------------------------------
> |> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> |> For additional commands, e-mail: axis-dev-help@ws.apache.org
> |>
> |>
> |
> |
> |
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDdwMgNg6eWEDv1kRAjPdAJ0TdqwjsTLvziHNa/9qC3z8HEkNfgCfQoZl
> qTBtDY480X1XTokdxoojlEg=
> =puTP
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> 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: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Under synapse...Sure. Perfect.
- -- dims
Paul Fremantle wrote:
| I agree there isn't any point keeping stale copies in Axis2. What
| about building a separate module or even commons-transports?
|
| Paul
|
| On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas <da...@gmail.com> wrote:
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|> Folks,
|>
|> Let's move JMS and Async NIO transports out of Axis2 into Synapse. There's
|> no point keeping a stale copy in Axis2.
|>
|> WDYT?
|>
|> Thanks,
|> dims
|> -----BEGIN PGP SIGNATURE-----
|> Version: GnuPG v1.4.5 (Cygwin)
|>
|> iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
|> nJ5rX+dn2iaC7Fs9/+C+1LE=
|> =/TIB
|> -----END PGP SIGNATURE-----
|>
|> ---------------------------------------------------------------------
|> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
|> For additional commands, e-mail: axis-dev-help@ws.apache.org
|>
|>
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDdwMgNg6eWEDv1kRAjPdAJ0TdqwjsTLvziHNa/9qC3z8HEkNfgCfQoZl
qTBtDY480X1XTokdxoojlEg=
=puTP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2
into Synapse
Posted by Davanum Srinivas <da...@gmail.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Under synapse...Sure. Perfect.
- -- dims
Paul Fremantle wrote:
| I agree there isn't any point keeping stale copies in Axis2. What
| about building a separate module or even commons-transports?
|
| Paul
|
| On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas <da...@gmail.com> wrote:
|> -----BEGIN PGP SIGNED MESSAGE-----
|> Hash: SHA1
|>
|> Folks,
|>
|> Let's move JMS and Async NIO transports out of Axis2 into Synapse. There's
|> no point keeping a stale copy in Axis2.
|>
|> WDYT?
|>
|> Thanks,
|> dims
|> -----BEGIN PGP SIGNATURE-----
|> Version: GnuPG v1.4.5 (Cygwin)
|>
|> iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
|> nJ5rX+dn2iaC7Fs9/+C+1LE=
|> =/TIB
|> -----END PGP SIGNATURE-----
|>
|> ---------------------------------------------------------------------
|> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
|> For additional commands, e-mail: axis-dev-help@ws.apache.org
|>
|>
|
|
|
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Cygwin)
iD8DBQFIDdwMgNg6eWEDv1kRAjPdAJ0TdqwjsTLvziHNa/9qC3z8HEkNfgCfQoZl
qTBtDY480X1XTokdxoojlEg=
=puTP
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Paul Fremantle <pz...@gmail.com>.
I agree there isn't any point keeping stale copies in Axis2. What
about building a separate module or even commons-transports?
Paul
On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas <da...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Folks,
>
> Let's move JMS and Async NIO transports out of Axis2 into Synapse. There's
> no point keeping a stale copy in Axis2.
>
> WDYT?
>
> Thanks,
> dims
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
> nJ5rX+dn2iaC7Fs9/+C+1LE=
> =/TIB
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2][Proposal] Move JMS / Async NIO transports out of Axis2 into Synapse
Posted by Paul Fremantle <pz...@gmail.com>.
I agree there isn't any point keeping stale copies in Axis2. What
about building a separate module or even commons-transports?
Paul
On Tue, Apr 22, 2008 at 1:32 PM, Davanum Srinivas <da...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Folks,
>
> Let's move JMS and Async NIO transports out of Axis2 into Synapse. There's
> no point keeping a stale copy in Axis2.
>
> WDYT?
>
> Thanks,
> dims
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.5 (Cygwin)
>
> iD8DBQFIDdrAgNg6eWEDv1kRAt0hAKCL8ot+QCGAPGEJ9/OisXYnQXhs7wCgoFq7
> nJ5rX+dn2iaC7Fs9/+C+1LE=
> =/TIB
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair
blog: http://pzf.fremantle.org
paul@wso2.com
"Oxygenating the Web Service Platform", www.wso2.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org