TomEE w/ ActiveMQ 6

["John D. Ament" <jo...@apache.org>]

Hi,

So yesterday the JMS 2.0 spec JAR was brought in to Geronimo.  Thanks
Romain for merging!

I started hacking w/ ActiveMQ 6 to make sure the JAR worked.  They look
good.  For those unaware, ActiveMQ 6 == JBoss HornetQ.  Unfortunately, it
looks like they don't plan to support all of the internal APIs people may
have used to bootstrap ActiveMQ previously, so code changes are required.

I started looking at TomEE's ActiveMQ integration to see how bad it is.
After a couple of hours of hacking, I have something compiling at least.
No tests pass, but it compiles at least.

https://github.com/johnament/tomee/commit/a5f7c362b3a176c720ea3f37ea77ae48bf53dcdf

So are there any plans to support ActiveMQ 6 w/ JMS 2.0 APIs in TomEE
Plus?  Since this is basically a completely different beast (with the same
name) everything will need to be looked at - including how to configure
within the app server.  I'd be happy to contribute back my changes once
they actually work.

One weird thing I saw was that there's two places where ActiveMQ
integration occurs, however only one is actually included in the
distribution.  Is that on purpose?  One is in the openejb-core and the
other in server/openejb-activemq.  Can the activemq integration be
consolidated down to openejb-activemq and have that registered within the
distribution?

John

Re: TomEE w/ ActiveMQ 6

[Romain Manni-Bucau <rm...@gmail.com>]

Hi John

Le 3 janv. 2015 14:17, "John D. Ament" <jo...@apache.org> a écrit :
>
> Hi,
>
> So yesterday the JMS 2.0 spec JAR was brought in to Geronimo.  Thanks
> Romain for merging!
>
> I started hacking w/ ActiveMQ 6 to make sure the JAR worked.  They look
> good.  For those unaware, ActiveMQ 6 == JBoss HornetQ.  Unfortunately, it
> looks like they don't plan to support all of the internal APIs people may
> have used to bootstrap ActiveMQ previously, so code changes are required.
>

AFAIK this is not HornetMQ but really a merge of both.

> I started looking at TomEE's ActiveMQ integration to see how bad it is.
> After a couple of hours of hacking, I have something compiling at least.
> No tests pass, but it compiles at least.
>
>
https://github.com/johnament/tomee/commit/a5f7c362b3a176c720ea3f37ea77ae48bf53dcdf
>
> So are there any plans to support ActiveMQ 6 w/ JMS 2.0 APIs in TomEE
> Plus?  Since this is basically a completely different beast (with the same
> name) everything will need to be looked at - including how to configure
> within the app server.  I'd be happy to contribute back my changes once
> they actually work.
>

Sure, we dont have the choi e I fear.

> One weird thing I saw was that there's two places where ActiveMQ
> integration occurs, however only one is actually included in the
> distribution.  Is that on purpose?  One is in the openejb-core and the
> other in server/openejb-activemq.  Can the activemq integration be
> consolidated down to openejb-activemq and have that registered within the
> distribution?
>

Integration is in core, other one is linked to another usage i never saw in
companies.

Historically it is in the core to bring it by default. It is not in web
profile just to be able to get certified but that is really just a
packaging hack not matching our philosophy/design.

Integration is mainly service-jar.xml and broker lifecycle handling in the
resource adapter (embedded or not)

> John