On 28.01.2010 23:38, Jean-Louis MONTEIRO wrote:
Hey Andy,
sorry for the very long delay.
Firstly, i believed we could refactor some activemq integration before
checking in your patch.
But, to be honest, i'm not really happy with that refactoring because it
makes things more complicated.
So i plan to CI your patch asap (thx again for the good job).
If we all agree, i gonna just rename the prefix as proposed by David
(amq4factory and amq5factory).
But i'd really like to keep backward compatibility. So, can you have a look
on how we can still use openejb: prefix?
If you have other topics/jira/features you want to work on, feel free to
push a post, a jira, a patch ... I'd be more than happy to commit it for
you. Help is always welcome.
Jean-Louis
I was working on this as your email came in.
I shall post a revised patch at
https://issues.apache.org/jira/browse/OPENEJB-1227 within the next half
hour.
Changes:
Module renamed to: OpenEJB :: Container :: ActiveMQ4
Artifact renamed to: openejb-activemq4
Prefix:
openejb - loads org.apache.openejb.resource.activemq.ActiveMQ5Factory
amq5factory- loads
org.apache.openejb.resource.activemq.ActiveMQ5Factory
amq4factory - loads
org.apache.openejb.resource.activemq.ActiveMQ4Factory
As far as I know the 'openejb' properties can only contain one 'class'
entry, so this is to be (as stated above) ActiveMQ5Factory.
____________
Virus checked by G Data AntiVirus
Version: AVA 19.9823 dated 28.01.2010
