Yes, that is correct, please see the packaging example though.
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3834216#3834216
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3834216
Hi there,
Been asked by Bill to let you know he is away giving training. He'll respond
eventually, but not as quickly as normal.
Cheers,
Kab
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3834046#3834046
Reply to the post :
I'm running outised the app server and my jboss-aop.xml is properly loaded from the
META-INF directory but not the metadata-aop.xml. It seems that the metadata file only
gets propery loaded using the jboss.aop.path, is that right ?
View the original post :
Sorry about that, metadata-aop.xml was not in jboss.aop.path. Absolutely my fault.
Thinking about it this property bothers me a bit as in most deployment you don't have
a prior knowledge of the file system. Is there a way to make JBossAOP just look in the
classpath (like loading it using a
Depends if you are running inside or outside the JBoss application server.
If outside, then JBoss AOP does this by default:
Enumeration enum =
Thread.currentThread().getContextClassLoader().getResources(META-INF/jboss-aop.xml);
So any part of your classpath that has a
Trying again to post the pointcut declaration :
bind pointcut=all(@transactional)
|interceptor
class=org.smcp.twister.engine.common.aspect.TransactionInterceptor/
|/bind
|
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3833380#3833380
Did you look at the metadata example that comes with JBoss AOP beta1? You have to run
that generates another XML file. Then you must have that XML file and your binding
in the jboss.aop.path System property.
If you change to have report=true then you can get an XML dump of bindings and
