Conflicts between execution script and o.a.a.broker.Main class

I have not started to look at unix based start script, but I am finding some interesting issues with the one for use under Windows (activemq.bat).

This script is using the java –jar option that points to the ACTIVEMQ_HOME/bin/run.jar file. The manifest points to the o.a.a.broker.Main class.

Use of this execution option and review of the o.a.a.broker.Main class (where it sets up a classloader with classpath pointing to the conf, lib and lib/optional directories would lead one to believe that the o.a.a.broker.Main class would be loaded from run.jar. This is not the case as the script also defines the java property of “java.ext.dirs” to append the activemq directories. While it also sets the command line –classpath option, this is useless as including all the activemq directories will already include “all” activemq classes at the base classloader. This also includes a copy of the o.a.a.broker.Main class that is include in the “uber” activemq-4.0.jar in the ACTIVEMQ_HOME directory.

Also with the definition java.ext.dirs this will total obviate any setting of classpath information on the classloader (auto or parameter specified) by the o.a.a.broker.Main class.

Obviously something is not right here. If o.a.a.broker.Main class is suppose to be setting up the class loader, why is the script setting the java.ext.dir property and the –classpath option on the command line?