Can we please stop using html emails. Especially MSHTML. I tried to reply to this e-mail and got a screen.
Anyway. As I said before. The main constraint to using JBossRetro is fixing the AnnotationHelper to understand classloaders. Eventually, this should be linked with the ClassInfo abstraction, but that will likely require more work than what is currently required for AnnotationHelper to work. i.e. classloader == clazz.getClassLoader(); because AnnotationHelper knows the Class. The fix should basically be to copy what AOP does. If you like I can reproduce it. I had it working in the case where it is told the classloader. It is harder in the more general ClassInfo case where it has to determine the classloader for superclases/interfaces, etc. that are not already loaded. On Tue, 2006-03-14 at 15:39 -0600, Ryan Campbell wrote: Ok, I ran the webservices tests against a jbossretro-weaved jbossws14.sar and all the tests passed. Todo: - create a 1.0.RC1 for backport-concurrent, jbossretro so they can be added to the repository - officially integrate jbossretro into the jboss-head/webservices build - Create an 1.0.RC3 for jbossws14 from the jbossretro build - Integrate it with 4.0 This should be done by tomorrow, unless there are any objections. -- xxxxxxxxxxxxxxxxxxxxxxxx Adrian Brock Chief Scientist JBoss Inc. xxxxxxxxxxxxxxxxxxxxxxxx ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
