"[EMAIL PROTECTED]" wrote : The hard part about the GenericBeanFactory is creating all the metadata. Also, how about all the metadata overrides? I think this should be a separate API with the ClassAdapter instead of the way we proposed it in Boston. Not only would this get rid of the need for javassist to preprocess and create ClassInfo's, but it would also not force me to totally refactor (practically rewrite) jboss AOP to use ClassInfo's to bind aspects.
I've got to the stage where I don't care and just want something that works. :-) Even if it is just the simple use cases. Without something concrete to build on and write test cases to show missing features, it is just lots of arguments in the forums and more delays. I've already been through a couple of refactors (both the Bean model and xml) and still don't know what the final api looks like, that's why I call it an impass and started working on other things. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874360#3874360 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874360 ------------------------------------------------------- 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
