We are unifying the spi not the implementation. An interceptor doesn't care wether it woven in through byte code manipulation or behind a proxy.
1a) My question was what is the footprint. My concern is that the size of the jars if we are going to run on a system with limited space. Most of jboss-common and concurrent are not used. These jars could be very easily trimmed for a limited environment. 1b) java.lang.reflect.Proxy works in those environments. Yes you have to use reflection (which means some features will not be available as I said). 2) I mean where you don't have control of the security policy. These environments limit you to performing operations like classloading and reflection on co-deployed classes (same classloader - or a child classloader if you are allowed to create such a thing). Certainly things like modifying accessibility or byte code manipulation won't be allowed. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3863930#3863930 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3863930 ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
