[prev in list] [next in list] [prev in thread] [next in thread]
List: synapse-dev
Subject: Re: Bundling of transports with the distribution - what should be the default?
From: "Ruwan Linton" <ruwan.linton () gmail ! com>
Date: 2009-01-14 11:50:26
Message-ID: 672a01200901140338m235af898yaccfd66fa488b9ad () mail ! gmail ! com
[Download RAW message or body]
I also think that the fix transport has to be an optional one, any way we
are not shipping the dependencies of the fix transport, so why don't we keep
that off by default?
I am completely +1 for shipping the http/s, jms, mail and vfs.
Thanks,
Ruwan
On Wed, Jan 14, 2009 at 10:35 AM, Paul Fremantle <pzfreo@gmail.com> wrote:
> Good question!
>
> I support including http/s, jms, vfs, mail as defaults. I'm 50/50 on
> fix and xmpp (I could be persuaded of either approach). I agree amqp
> should be separate.
>
> Paul
>
> On Tue, Jan 13, 2009 at 10:22 AM, Asankha C. Perera <asankha@apache.org>
> wrote:
> > Hi All
> >
> > Although theoretically any Axis2 transport should work with Synapse,
> there
> > could very well be cases where some might not. To limit the distribution
> > size and dependencies, I thought we should bundle the main transports
> that
> > have been well tested over the past months, and which contains samples,
> and
> > where we could find at least one of us to support potential users. For
> the
> > other transports, we could make them available as optional bundles (maybe
> > even copy them into a lib/optional) but without other 3rd party
> > dependencies.
> >
> > The transports I am thinking of bundling by default are http/s, jms, vfs,
> > mail, fix. We could easily include the pipe, udp and tcp transports into
> > this list, and maybe Andreas could provide a simple sample for each of
> > these? I would like to hear your thoughts about amqp, xmpp and the local
> > transport - and if anyone thinks we should include these by default.
> >
> > I also restarted Hudson, and the build ran fine a few minutes ago.. Also
> > FYI, probably you have already noticed that mvn 2.0.9 wanted to download
> > some artifacts when running offline.. I switched to mvn 2.1.0-M1 a while
> > ago, and it seems like it behaves better for offline builds..
> >
> > cheers
> > asankha
> >
> > --
> > Asankha C. Perera
> > http://adroitlogic.org
> >
> > http://esbmagic.blogspot.com
> >
> >
> > ---------------------------------------------------------------------
> > 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
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
[Attachment #3 (text/html)]
I also think that the fix transport has to be an optional one, any way we are not \
shipping the dependencies of the fix transport, so why don't we keep that off by \
default? <br><br>I am completely +1 for shipping the http/s, jms, mail and vfs.<br> \
<br>Thanks,<br>Ruwan<br><br><div class="gmail_quote">On Wed, Jan 14, 2009 at 10:35 \
AM, Paul Fremantle <span dir="ltr"><<a \
href="mailto:pzfreo@gmail.com">pzfreo@gmail.com</a>></span> wrote:<br><blockquote \
class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt \
0pt 0.8ex; padding-left: 1ex;"> Good question!<br>
<br>
I support including http/s, jms, vfs, mail as defaults. I'm 50/50 on<br>
fix and xmpp (I could be persuaded of either approach). I agree amqp<br>
should be separate.<br>
<br>
Paul<br>
<div><div></div><div class="Wj3C7c"><br>
On Tue, Jan 13, 2009 at 10:22 AM, Asankha C. Perera <<a \
href="mailto:asankha@apache.org">asankha@apache.org</a>> wrote:<br> > Hi \
All<br> ><br>
> Although theoretically any Axis2 transport should work with Synapse, there<br>
> could very well be cases where some might not. To limit the distribution<br>
> size and dependencies, I thought we should bundle the main transports that<br>
> have been well tested over the past months, and which contains samples, and<br>
> where we could find at least one of us to support potential users. For \
the<br> > other transports, we could make them available as optional bundles \
(maybe<br> > even copy them into a lib/optional) but without other 3rd party<br>
> dependencies.<br>
><br>
> The transports I am thinking of bundling by default are http/s, jms, vfs,<br>
> mail, fix. We could easily include the pipe, udp and tcp transports into<br>
> this list, and maybe Andreas could provide a simple sample for each of<br>
> these? I would like to hear your thoughts about amqp, xmpp and the local<br>
> transport - and if anyone thinks we should include these by default.<br>
><br>
> I also restarted Hudson, and the build ran fine a few minutes ago.. Also<br>
> FYI, probably you have already noticed that mvn 2.0.9 wanted to download<br>
> some artifacts when running offline.. I switched to mvn 2.1.0-M1 a while<br>
> ago, and it seems like it behaves better for offline builds..<br>
><br>
> cheers<br>
> asankha<br>
><br>
> --<br>
> Asankha C. Perera<br>
> <a href="http://adroitlogic.org" target="_blank">http://adroitlogic.org</a><br>
><br>
> <a href="http://esbmagic.blogspot.com" \
target="_blank">http://esbmagic.blogspot.com</a><br> ><br>
><br>
> ---------------------------------------------------------------------<br>
> To unsubscribe, e-mail: <a \
href="mailto:dev-unsubscribe@synapse.apache.org">dev-unsubscribe@synapse.apache.org</a><br>
> For additional commands, e-mail: <a \
href="mailto:dev-help@synapse.apache.org">dev-help@synapse.apache.org</a><br> \
><br> ><br>
<br>
<br>
<br>
</div></div>--<br>
Paul Fremantle<br>
Co-Founder and CTO, WSO2<br>
Apache Synapse PMC Chair<br>
OASIS WS-RX TC Co-chair<br>
<br>
blog: <a href="http://pzf.fremantle.org" \
target="_blank">http://pzf.fremantle.org</a><br> <a \
href="mailto:paul@wso2.com">paul@wso2.com</a><br> <br>
"Oxygenating the Web Service Platform", <a href="http://www.wso2.com" \
target="_blank">www.wso2.com</a><br> <div><div></div><div class="Wj3C7c"><br>
---------------------------------------------------------------------<br>
To unsubscribe, e-mail: <a \
href="mailto:dev-unsubscribe@synapse.apache.org">dev-unsubscribe@synapse.apache.org</a><br>
For additional commands, e-mail: <a \
href="mailto:dev-help@synapse.apache.org">dev-help@synapse.apache.org</a><br> <br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Ruwan Linton<br><a \
href="http://wso2.org">http://wso2.org</a> - "Oxygenating the Web Services \
Platform"<br><a \
href="http://ruwansblog.blogspot.com/">http://ruwansblog.blogspot.com/</a><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic