I think the ant tasks could be completely independant of servicemix-core and servicemix-jbi. They use JMX, but we currently use a JMX proxy, so we need the interface, but we could easily use plain JMX calls (though it's more difficult to maintain). But source refactoring will not happen before 3.0, I' ve commented the JIRA for that (http://issues.apache.org/activemq/browse/SM-527) Do you really need to use ant ? because you could easily bypass the ant tasks as you are inside the JBI container.
On 8/9/06, Peter Klotz <[EMAIL PROTECTED]> wrote:
Hi, I'm trying to call SM Ant tasks (e.g. Deploy SA Task) from within a SU. The Ant-Jars are in the SU (because otherwise one could not call any other custom Ant task from within the ant task when the corresponding classes are in the SU). The problem is that the SM Ant tasks are in the servicemix-core-3.0-*.jar, which is required by SM of course. And because the classes of the tasks are already loaded in the SM-Classloader even putting the jar into the SU classpath does not solve the problem that the Ant Task-class is not found. A potential solution, not sure though, would be to put the SM Ant tasks into a separate jar file e.g. servicemix-ant-3.0-*.jar that one could put into the SM and not into the lib dir. I'll give this a try manually but would it be feasable in the next realease to split the ant tasks out of core? It seems that the ant tasks need servicemix-core (for the tasks itself), servicemix-jbi and mx4j-*. Thanks, Peter
-- Cheers, Guillaume Nodet
