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 <[EMAIL PROTECTED]> 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/> > | > > > - -- > 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"
