JBoss Microcontainer with JBoss AOP in a standalone app.

[pekarna]

Hi,

I'm trying to create a standalone app using JBoss Microcontainer for IoC and JBoss AOP for, well, AOP.
I've boot-strapped, deployed a descriptor with AOP XML, so far so good.
But the aspect is not performed. Do I need to enable AOP plugin ors something?

Please check the code below.

Thanks for help.

<deployment xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
 xsi:schemaLocation="urn:jboss:bean-deployer:2.0 bean-deployer_2_0.xsd"
 xmlns="urn:jboss:bean-deployer:2.0"
 xmlns:aop="urn:jboss:aop-beans:1.0">

 <bean name="myGarage" class="cz.zizka.ondra.jbmctest.Garage">
 <property name="car">
 <bean name="myCar" class="cz.zizka.ondra.jbmctest.Car">
 <property name="name">Red Devil</property>
 </bean>
 </property>
 </bean>

 <aop:interceptor name="FuelInterceptor" class="cz.zizka.ondra.jbmctest.FuelInterceptor"/>

 <aop:bind pointcut="execution(* cz.zizka.ondra.jbmctest.Car->set*Fuel(..)">
 <aop:interceptor-ref name="FuelInterceptor"/>
 </aop:bind>

</deployment>

 public static void main( String[] args ) throws Throwable
 {
 // Bootstrap.
 BasicBootstrap bootstrap = new BasicBootstrap();
 bootstrap.run();

 // Load the bean definitions.
 URL url = Thread.currentThread().getContextClassLoader().getResource("jboss-beans.xml");
 BasicXMLDeployer deployer = new BasicXMLDeployer( bootstrap.getKernel() );
 deployer.deploy( url );

 KernelController cont = bootstrap.getKernel().getController();
 ControllerContext context = cont.getInstalledContext("myGarage");
 System.out.println( "I have a garage: "+context.getTarget());

 // Put some fuel in.
 Car myCar = (Car) cont.getInstalledContext("myCar").getTarget();
 myCar.setLitresOfFuel( myCar.getLitresOfFuel() + 1 );
 System.out.println( "I have a garage: "+context.getTarget());


 deployer.shutdown();

 }

public class FuelInterceptor implements Interceptor {

 private static final Logger log = Logger.getLogger( FuelInterceptor.class.getName() );

 public Object invoke(Invocation invocation) throws Throwable
 {
 System.out.println( "In FuelInterceptor." );
 if( true ) throw new Exception(); // To see that it's really NOT called.
 Object target = invocation.getTargetObject();
 long time = System.currentTimeMillis();
 log.info("Invocation [" + target + "] start: " + time);
 try{
 return invocation.invokeNext();
 }
 finally{
 log.info("Invocation [" + target + "] time: " + (System.currentTimeMillis() - time));
 }
 }

 public String getName() {
 return FuelInterceptor.class.getName();
 }
}// class FuelInterceptor

[pekarna]

Note that I don't use any precompiler - Ant's or Maven plugin - I want it to work like Spring AOP, i.e. all done at runtime.

[kabirkhan]

You probably forgot to turn on loadtime weaving http://www.jboss.org/jbossaop/docs/2.0.0.GA/docs/aspect-framework/reference/en/html/running.html#running-as-sun-jdk

[ozizka]

Hi Kabir, thanks, solved. I didn't realize that JBoss AOP differs from Spring AOP in the principles - not a proxy-based AOP, thus it needs either compile-time weaving or the JVM -javaagent.

I ran into an issue with compile time weaving: It does not understand the document (with namespaced AOP delements):

java.lang.IlleÂÂgalArgumentExÂÂception: Unknown AOP tag: bean

Is there a way to have just one config file and use it with the maven AOP plugin?

[kabirkhan]

I take it you're mixing aop and mc bean stuff in one file. Unfortunately that is not possible in plain aop. Although, patching aop for your needs should be trivial

 private void deployTopElements(Element top)
 throws Exception
 {
 NodeList children = top.getChildNodes();
 for (int i = 0; i < children.getLength(); i++)
 {
 if (children.item(i).getNodeType() == Node.ELEMENT_NODE)
 {
 Element element = (Element) children.item(i);
 String tag = element.getTagName();
 if (tag.equals("interceptor"))
 {
 deployInterceptor(element);
 }
 ....
 else if (tag.equals("arraybind"))
 {
 deployArrayBinding(element);
 }
 else
 {
 throw new IllegalArgumentException("Unknown AOP tag: " + tag);
 }
 }
 }
 }

Just comment out the throw. I'm not 100% sure how that would work with the maven plugin, I'll ask Ståle

[kabirkhan]

The method I posted above belongs to AspectXMLLoader

[stalep]

it shouldnt have any affect on the mavenplugin. the plugin just creates a new thread and calls jboss-aop for you with all the options.