This content has been marked as final.
Show 6 replies
-
1. Re: class incompatibilites b/w JBM 1.4 and JBM 2
timfox Jan 13, 2009 12:25 PM (in response to jmesnil)"jmesnil" wrote:
Clebert suggested to rename the package org.jboss.messaging.util to org.jboss.messaging.utilities to avoid any further clash.
+1
or org.jboss.messaging.common -
2. Re: class incompatibilites b/w JBM 1.4 and JBM 2
timfox Jan 13, 2009 12:28 PM (in response to jmesnil)Furthermore - we should ensure there is zero overlap between any other 1.x and 2.x class names as this may cause other subtle issues when running both sets of classes in the same classloader.
-
3. Re: class incompatibilites b/w JBM 1.4 and JBM 2
jmesnil Jan 13, 2009 12:37 PM (in response to jmesnil)i'll rename it to o.j.messaging.utilities.
as far as i checked there were no other clashes:
JMS code is in o.j.jms in 1.4 while JBM 2 code is in o.j.messaging.jms
Both version use o.j.messaging.core but JBM 1.4 code is below "impl" subpackage while JBM2 is splitted in many subpackages
I'll do a thorough check to be sure that there is no other class clashes than the util package -
4. Re: class incompatibilites b/w JBM 1.4 and JBM 2
clebert.suconic Jan 13, 2009 12:52 PM (in response to jmesnil)"timfox" wrote:
Furthermore - we should ensure there is zero overlap between any other 1.x and 2.x class names as this may cause other subtle issues when running both sets of classes in the same classloader.
Can't we rename the whole base package? (org.jboss.messaging to something else?)
I have been there when we had to play with SAR isolations and it wasn't any fun. I foresee users using both JBM 1.4 and JBM 2.0 on the same VM during migrations... and it would be better to be completely isolated.
We could verify of course if there are no clashes.. but if renaming the package is acceptable.. that would give us some peace of mind. -
5. Re: class incompatibilites b/w JBM 1.4 and JBM 2
timfox Jan 13, 2009 1:09 PM (in response to jmesnil)"clebert.suconic@jboss.com" wrote:
Can't we rename the whole base package? (org.jboss.messaging to something else?)
Yes. I suggest org.jboss.jbm.*
But don't do it now, since it will cause a merge nightmare for anyone working on stuff. Let's add a JIRA and do at it then end.