You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@activemq.apache.org by "Alan D. Cabrera" <li...@toolazydogs.com> on 2007/02/11 20:28:12 UTC
Re: backport-util-concurrent ?
On Jan 31, 2007, at 8:30 AM, Christopher G. Stach II wrote:
> GaryG wrote:
>> Hello,
>>
>> I just started playing with AMQ 4.1.0 and realized that I had to
>> include the
>> backport-util-concurrent.jar file to run it. I'm just wondering
>> why AMQ
>> needs to use a backported version of the concurrency classes.
>
> For pre-1.5.0 JVMs. That'll be dropped in AMQ 5.0 (aka AMQ 4.2).
If we drop our use of backport, how will we be able to use
retroweaver to run on JDK14?
Regards,
Alan
Re: backport-util-concurrent ?
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
Cool so there's some way to get it working on JDK14.
Regards,
Alan
On Feb 11, 2007, at 11:57 AM, Jason Dillon wrote:
> If you just use the concurrent bits from 1.5, then you can use
> retrotranslator to take those 1.5 classes and run them on 1.4 with
> retrotranslator-runtime-n.n.n.jar and backport-util-concurrent-
> n.n.jar into the classpath of the application.
>
> So you could drop having the normal codebase using the backport
> classes directly, and let translation map things up properly for
> 1.4 support.
>
> Dunno about the weaver though... have never used it.
>
> --jason
>
>
> On Feb 11, 2007, at 11:28 AM, Alan D. Cabrera wrote:
>
>>
>> On Jan 31, 2007, at 8:30 AM, Christopher G. Stach II wrote:
>>
>>> GaryG wrote:
>>>> Hello,
>>>>
>>>> I just started playing with AMQ 4.1.0 and realized that I had to
>>>> include the
>>>> backport-util-concurrent.jar file to run it. I'm just wondering
>>>> why AMQ
>>>> needs to use a backported version of the concurrency classes.
>>>
>>> For pre-1.5.0 JVMs. That'll be dropped in AMQ 5.0 (aka AMQ 4.2).
>>
>> If we drop our use of backport, how will we be able to use
>> retroweaver to run on JDK14?
>>
>>
>> Regards,
>> Alan
>>
>>
>
>
Re: backport-util-concurrent ?
Posted by Jason Dillon <ja...@planet57.com>.
If you just use the concurrent bits from 1.5, then you can use
retrotranslator to take those 1.5 classes and run them on 1.4 with
retrotranslator-runtime-n.n.n.jar and backport-util-concurrent-
n.n.jar into the classpath of the application.
So you could drop having the normal codebase using the backport
classes directly, and let translation map things up properly for 1.4
support.
Dunno about the weaver though... have never used it.
--jason
On Feb 11, 2007, at 11:28 AM, Alan D. Cabrera wrote:
>
> On Jan 31, 2007, at 8:30 AM, Christopher G. Stach II wrote:
>
>> GaryG wrote:
>>> Hello,
>>>
>>> I just started playing with AMQ 4.1.0 and realized that I had to
>>> include the
>>> backport-util-concurrent.jar file to run it. I'm just wondering
>>> why AMQ
>>> needs to use a backported version of the concurrency classes.
>>
>> For pre-1.5.0 JVMs. That'll be dropped in AMQ 5.0 (aka AMQ 4.2).
>
> If we drop our use of backport, how will we be able to use
> retroweaver to run on JDK14?
>
>
> Regards,
> Alan
>
>