Hi devs, we've been working heavily with Romain those latest days. We'd like to discuss about pruning some parts (unmaintained sometimes).
As you may know, the spec introduce such a vocabulary, and I guess that we should consider pruning some parts in the next major release 4.0.0 For examples : Axis and Axis2 implementation don't work AFAIR and are never maintained. There is also ActiveMQ 4 which has a lot of classes copied from the trunk and IMHO, it does not make sense to keep it in 4.0.0. Otherwise, we should consider some refactoring using the Reflect API for legacy support (like Tomcat 5). OpenEJB Spring is more a proof of concept but is it really used and useful? openejb-webadmin: has never been maintained since I have been involved ;-) And probably more modules. Instead, I would like to suggest an openejb-utils module because we have a lot of utility classes used in different modules and then we have to duplicate them. Last but not least, may be we should think about some refactoring linked to OSGi requirements. Thoughts? Feedback is more than welcome ;-) Regards, Jean-Louis -- View this message in context: http://openejb.979440.n4.nabble.com/Pruning-OpenEJB-project-and-co-tp3686410p3686410.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
