synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ruwan Linton" <ruwan.lin...@gmail.com>
Subject Re: Synapse 1.2 beta1
Date Tue, 03 Jun 2008 05:13:11 GMT
Hi all,

I guess there is no issue with keeping the AMQP transport with the release
as an experimental transport but we can remove the Qpid jars at the
distribution build time so that one needs to copy the relevant jars in to
the lib folder to get it working.

Hope this is OK. I am going to remove the Qpid jars from the distribution
for the 1.2 release.

Thanks,
Ruwan

On Thu, May 29, 2008 at 11:34 PM, Rajith Attapattu <rajith77@gmail.com>
wrote:

> Ruwan,
>
> I think the best option is to remove the AMQP transport code from the  1.2
> branch.
> As Suran pointed you guys can use M2.1 release from Qpid and use that with
> the JMS transport.
> M2.1 is an official release and it makes sense to go with this for this
> Syanpse release.
> Also this will encourage folks to use it as its based on an official
> release.
>
> I can finalize the transport on trunk. And hopefully by the time Synapse
> makes the next release M3 will be ready.
> We are also going to ensure the M3 client will interoperate with the M2.1
> broker.
> So if somebody is going to use this in production, upgrading to the next
> Synapse release will not cause any issues.
>
> Regards,
>
> Rajith
>
> On Thu, May 29, 2008 at 12:53 PM, Paul Fremantle <pzfreo@gmail.com> wrote:
>
> > Ruwan
> >
> > The problem is that M3 doesn't exist yet. The issue here is that
> > Rajith has been working on 'experimental' code, which is really cool,
> > but unfortunately it clashes with using the stable Qpid build. Since
> > the M2.1 broker is meant to be "production" ready, I propose we need
> > to go back to the M2.1 JARs if we want people to be able to use
> > Qpid/AMQP in a stable production environment.
> >
> > Paul
> >
> >
> > On Thu, May 29, 2008 at 5:03 PM, Ruwan Linton <ruwan.linton@gmail.com>
> > wrote:
> > > Hi Suran,
> > >
> > > I think this is normal if you do critical changes on the API and also
> > Qpid
> > > is still at milestone releases and hence you cannot expect one
> milestone
> > to
> > > be compatible with the other. So if you want to connect to a particular
> > > version of Qpid (this is the case for most of the other brokers as
> well)
> > you
> > > should be using the client jars from that particular version.
> > >
> > > We cannot do much with that :-)
> > >
> > > Thanks,
> > > Ruwan
> > >
> > > On Thu, May 29, 2008 at 8:23 PM, Suran Jayathilaka <suran@wso2.com>
> > wrote:
> > >
> > >> -----BEGIN PGP SIGNED MESSAGE-----
> > >> Hash: SHA1
> > >>
> > >> Hi,
> > >>
> > >> I was unable to connect to a Qpid/Java M2.1 broker with the M3 Qpid
> > client
> > >> jars packaged with the synapse distro. Replacing the qpid-client*.jar
> > and
> > >> qpid-common*.jar with
> > >> ~ the equvivalent from the Qpid/Java M2.1 distro fixed this for me.
> > >>
> > >> Thanks.
> > >> Suran
> > >>
> > >> Ruwan Linton wrote:
> > >> | Hi folks,
> > >> |
> > >> | I have created the Synapse-1.2-beta1 build and hosted it at [1]
> > according
> > >> to
> > >> | the plan we had.
> > >> |
> > >> | Please note that this is just a test build which will most probably
> go
> > as
> > >> | the RC if there are no issues in it (except for few documentation
> > >> changes)
> > >> | just after the Rampart release.
> > >> |
> > >> | Please test this build and provide your feedback on this build.
> > >> |
> > >> | Thanks,
> > >> | Ruwan
> > >> |
> > >> | [1] - http://people.apache.org/~ruwan/synapse/1_2/beta1/<http://people.apache.org/%7Eruwan/synapse/1_2/beta1/>
> <http://people.apache.org/%7Eruwan/synapse/1_2/beta1/>
> > <http://people.apache.org/%7Eruwan/synapse/1_2/beta1/>
> > >> |
> > >>
> > >>
> > >> - --
> > >> U. Suran Jayathilaka
> > >> WSO2, Inc. - http://www.wso2.com
> > >>
> > >> http://suranjay.blogspot.com
> > >> -----BEGIN PGP SIGNATURE-----
> > >> Version: GnuPG v1.4.6 (GNU/Linux)
> > >> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
> > >>
> > >> iD8DBQFIPsNiXkt94l6LfXURAkjKAKCqKEozYtbJmw9WbuqVZDZ5AJSCOgCgldKF
> > >> Lr4uVcTjTuXbUm7ILaXX/IY=
> > >> =vsZ9
> > >> -----END PGP SIGNATURE-----
> > >>
> > >>
> > >
> > >
> > > --
> > > 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: dev-unsubscribe@synapse.apache.org
> > For additional commands, e-mail: dev-help@synapse.apache.org
> >
> >
>
>
> --
> Regards,
>
> Rajith Attapattu
> Red Hat
> http://rajith.2rlabs.com/
>



-- 
Ruwan Linton
http://www.wso2.org - "Oxygenating the Web Services Platform"

Mime
View raw message