The warning can probably be ignored. It means that somewhere the MSVoyagerClassLoader references the PolicyEngine class which is not on the classpath. Since your application works without AOP, this part of code is not ececuted and can probably be ignored.
Are you saying that Voyager has its own special classloaders that need to be used? If this is the case, do not use the aop SystemClassLoader. Try -Xbootclaspath (JDK 1.4) or -javaagent (JDK 5) instead http://labs.jboss.com/portal/jbossaop/docs/1.5.0.GA/docs/aspect-framework/reference/en/html/running.html#d0e2849 anonymous wrote : | Also, if a migrating POJO moves to a new location with it's annotated aspect, would it need to have the aop classloader running on the new location in order for the annotated aspects to work? | Either that or the classes would need to be precompiled. anonymous wrote : | Finally, when running an annotated aspect you need to specify the directory where the annotated class would be i.e. | | java -Djava.system.class.loader=org.jboss.aop.standalone.SystemClassLoader -Djboss.aop.class.path=c:\jbossaop2\jboss-aop_1.5.1.GA\docs\aspect-framework\examples\annotated-aspects\ Driver | | This is also causing a problem.... | I want to help, but if you read this first it will save us all some time: http://wiki.jboss.org/wiki/Wiki.jsp?page=JBossHelp View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3977850#3977850 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3977850 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
