Thanks Luciano for taking care of this one. On Wed, Dec 10, 2008 at 2:21 PM, Luciano Resende <[EMAIL PROTECTED]>wrote:
> I have locally moved all ActiveMQ dependencies to 5.1.0 and with > that, the BPEL helloworld sample works fine. I can give a quick try to > have 5.2.0 and commit the changes in the morning my time... > > On Wed, Dec 10, 2008 at 12:43 AM, ant elder <[EMAIL PROTECTED]> wrote: > > > > > > On Wed, Dec 10, 2008 at 7:08 AM, Luciano Resende <[EMAIL PROTECTED]> > > wrote: > >> On Tue, Dec 9, 2008 at 2:49 AM, ant elder <[EMAIL PROTECTED]> wrote: > >>> Another fix could be to move up to one of the ActiveMQ 5.x jars which > >>> don't > >>> include derby. > >>> > >> > >> I'm trying to move all activeMQ dependencies to 5.1.0 to see if this > >> solve the issue. While trying this, I noticed that we have different > >> versions of activeMQ dependencies across different projects (e.g from > >> 4.1.1 to 5.2.0)... is there any reason for having multiple versions of > >> the activeMQ depedency ? Would it be ok to move them all to a single > >> version such as 5.1.0 ? Or maybe to the latest 5.2.0 ? > >> > > > > Whether or not it happens for 1.4 I don't know of any reason we couldn't > > move up to a consistent use of 5.2.0. I think the mixture just happened > over > > time as people used which ever was current. There is an issue using SCA > > callbacks with JMS temporary destinations with AMQ 4.1.1 which is fixed > in > > 5.x so moving up would avoid any issues with that. > > > > ...ant > > > > > > -- > Luciano Resende > Apache Tuscany, Apache PhotArk > http://people.apache.org/~lresende <http://people.apache.org/%7Elresende> > http://lresende.blogspot.com/ > -- Thanks & Regards, Ramkumar Ramalingam
