2 Replies Latest reply on Jun 30, 2005 1:05 PM by Ryan McDonough

    Duplicate AspectManager Issues with SystemClassLoader in 1.3

    Ryan McDonough Newbie

      We're using JBoss AOP standalong under Java 1.4.2 and we're having some issues with 1.3. We're executing our code using:

      java -Djava.system.class.loader=org.jboss.aop.standalone.SystemClassLoader -Djboss.aop.path=project/jboss-aop.xml foo.Main

      This has been working for us, acutually the only way we could get it to work was declaring the VM to use the JBoss classloader. Anyway, under 1.3 the app throws a ClassNotFoundException and the stack reveals that there is a duplicate entry of the AspectManager in the class path. I have only the JDK14 AO classes in the path so I'm confused.

      If there's a better alternative to using the SystemClassLoader, I'm all ears. Also on a lighter note, the index.html is mising from the 1.3 JavaDocs.