jboss.aop.class.path is only really for standalone applications. As long as your target classes are prepared (i.e. have the hooks woven in), you should be able to deploy these as-is (war, ear etc.), and deploy the aspects in a separate .aop file. The only things we annotate are the aspects, i.e. they contain the bindings, aspect definitions etc., so this should not have any influence on your target application?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3929626#3929626 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3929626 ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
