Hi, Yes xbean.xml is a pure Spring beans file.
It means that, in your SU, if you add a dependency (in the POM for example) to the spring-aop and aopalliance libs, you can use AOP in the xbean.xml.
Nevertheless, as each SU has its own classloader (by default), I think the best way is to add AOP definition in each xbean.xml.
To be honest, I have never try this but it should work :) Regards JB akshay_ajmani wrote:
I had a query regarding using spring aspects with service mix. I read online and on the apache service discussion forums that each apache service unit is indirectly a spring configuration. We have an application in which we plan to use spring aspects so that we could do some logging (log4j) before invocation of some methods. This application has several SU’s with each SU has its own xml file i.e xbean.xml or camel service unit having camel-context.xml. I was thinking of defining spring aspects in each of these xml files. Can you please suggest to me if this is the best approach available or is there any other approach. I thank you once again for your time.
-- Jean-Baptiste Onofré --------------------------------- HomePage http://www.nanthrax.net --------------------------------- Contacts [email protected] [email protected] --------------------------------- OpenSource BuildProcess/AutoDeploy http://buildprocess.sourceforge.net Apache ServiceMix http://servicemix.apache.org ----------------------------------- PGP : 17D4F086
