That's great! I'm sorry that I neglected this note (I was only listing things that hadn't been done).
Would it be possible to get a Contributor License Agreement signed? I'm not 100% sure its necessary, but for a change of this size, it would be nice to cover the bases. By submitting a patch, you will be irrevocably reassigning copyright ot the Apache Software Foundation and allowing the code to be part of HiveMind and licenced as ASL. (Yes, I'm in Cover-Your-Ass mode here, but it's necessary). On Mon, 27 Dec 2004 23:33:10 +0100, Achim Huegen <[EMAIL PROTECTED]> wrote: > I would like to add jmx support. > Core jmx support is quite stable already and could be added easily in 1.1. > The metadata support (especially servicepoint construction info) may get > deferred to 1.2. > My jmx code already includes a change that allows enumeration of service > points, may be it is sufficient. > > Achim Huegen > > Am Mon, 27 Dec 2004 16:37:08 -0500 schrieb Howard Lewis Ship > <[EMAIL PROTECTED]>: > > > Time, I think, to start closing down new features and get ready for a > > beta. Again, the point of a beta is to close of the development of new > > functionality and focus on stability, documentation and bug fixing. > > > > Here's my list of thinks I'd like to see in HiveMind 1.1: > > > > <interceptor-set> - apply a set of interceptors to a wide range of > > HiveMind services. > > > > prototype service model (create a new instance for each method > > invocation) > > > > Enumerate services. Ability to list the full ids of all HiveMind > > services. Rod (Johnson) thinks this is necessary to properly > > integrate with Spring. > > > > Improve/fix HiveDoc. HiveDoc is now really ugly (sorry), need someone > > to really take ownership of this ... someone who understands XSLT and > > can do some decent design (not my forte!). > > > > Hydra - allow a single service implementation to be shared by multiple > > service points. Not sure what this would look like! It's just that, > > occasionally, it would be nice for one piece of logic to have more > > than one "face". This may get deferred out to 1.2. > > > > Conditional contributions -- I've already started on this. > > > > Serializable Services --- the service proxy should be > > Serializable/Externalizable. A placeholder object should be written > > out. On de-serialize, the placeholder should locate a Registry > > (inside a well known ThreadLocal) and replace itself. This isn't for > > serializaing services, per-se, but to allow data objects that contain > > references to services to be serialized. This comes up a lot in web > > applications, where objects end up in the HttpSession. > > > > Dynamic locale. Should be possible to change the Locale (on a > > thread-specific basis) and have messages automatically change over to > > the selected Locale. Currently, Locale is fixed at Registry build > > time ... it should be maleable at runtime. > > > > Votes? Discussions? Other ideas? > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
