Ok, shit, now I remember why AOP needed to create ClassInfos. Because of annotation overrides at the class level by the AOP container.
Yeah, I think MC should handle @Dependency, but ClassAdaptor will provide the ClassInfos (with overrides). Really I think the annotation override facility in JBoss AOP should be extracted into its own module so that MC can reuse it. It would be silly to map between ObjectModels that are doing the same thing. Anyways. let's iterate. I need to iterate because I can't focus on this stuff continuously because of other responsibilities (i.e. EJB3). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3871420#3871420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3871420 ------------------------------------------------------- This SF.net email is sponsored by Microsoft Mobile & Embedded DevCon 2005 Attend MEDC 2005 May 9-12 in Vegas. Learn more about the latest Windows Embedded(r) & Windows Mobile(tm) platforms, applications & content. Register by 3/29 & save $300 http://ads.osdn.com/?ad_id=6883&alloc_id=15149&op=click _______________________________________________ JBoss-Development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-development
