*Have* to deploy as an *.aop file?

[squeak]

I have an exisiting system where I am investigating using JBoss AOP to do TX demarcation.

All I am using right now is the annotations for Transactions.

If I first use the Annotation Compiler, and then the AopC compiler to instrument the classes before being deployed, is there any reason that it will still need to be loaded by the AOP deployer, and thus can stay as an EAR file? At that point, haven't I mutated the bytecode all that is nessecary, and it can just run as normal?

Or is there another aspect I am missing to this?

[kabirkhan]

Yes, there are two parts to this.

First the copiletime/loadtime instrumentation of the bytecode is done (done by the compilers)

Next, when running the instrumented app, the aop info must be present since it contains the info for building the Class-/InstanceAdvisors that contain what aspects are bound to what joinpoints.

Cheers,

Kabir

[bill.burke]

Squeak, does deploying an EAR alone with precompiled classes not work? It should. A .aop file is not needed.

[squeak]

"Bill Burke" wrote:
Squeak, does deploying an EAR alone with precompiled classes not work? It should. A .aop file is not needed.

Sorry, Bill. I haven't tried it yet, mainly because I am still having issues witt the AopC ant task mentioned in the other thread.

Also, I am trying to fundementally understand all of the different components, and how they work.

Thanks for the information!

BTW, the documentation doesn't make it clear that if all you are using is the Aspect Library, that you also need to include the base-aop.xml in the path for the AopC ant task.