"[EMAIL PROTECTED]" wrote : | | My thinking was the class adapter would go through something like the following logic: | | Object implements Advised -> InstanceAdvisor | (!Object implements Advised) && canWeave -> Runtime Weaving | (!Object implements Advised) && canWeave == false -> ProxyAdvisor | | With this being transparent to the "user", i.e. me JMX. | |
In your example the Class adaptor not only has to do the above, but also is it already woven. We do not want to do all this pre-processing at class load time or this "lightweight" container will take forever to boot up. The slow pre-processing is the same reason I did not want to have javassist create ClassInfo structures. anonymous wrote : | This is one of those backward compatibility requirements. This is far from a backward compatibility requirement considering we don't have an official @MBean implementation. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874355#3874355 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874355 ------------------------------------------------------- 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 JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
