jboss-aop.deployer holds a couple of things: the JBoss AOP runtime: Aspects are bound when classes are LOADED even with precompilation. What AOPC does is to preprocess the bytecode to weave in the hooks. The aspects are not bound until runtime. The is late-binding.
Late-binding is important for a lot of reasons. ONe of which being you can configure your aspects and which aspects are bound on a per-deployment basis, but still not get the overhead of load-time transformation. Hope I am making sense. Bill View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866275#3866275 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866275 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
