I often see people (like me :) asking for direct access to the registry. (I
know it's not the preferred way to use hivemind but sometimes it would be
really useful.)
What do you think about it?
BR,
Norbi
----- Original Message -----
From: "Howard Lewis Ship" <[EMAIL PROTECTED]>
To: "Knut Wannheden" <[EMAIL PROTECTED]>
Cc: <hivemind-dev@jakarta.apache.org>
Sent: Monday, January 16, 2006 5:16 PM
Subject: Re: hivemind update
I'd like to get 1.1.1 out the door, but there's something screwey with
GroovyBuilder. Can we, perhaps, deperecate GB and move it out to a
seperate project (maybe on JavaForge). We can even use the existing
Tapestry @ JavaForge site.
In terms of the rest ... we should discuss these things in public on
the developer list.
Things I want (no order)
JDK 1.5 / Annotations & Generics support
Specify default factory service for a module (to override
hivemind.BuilderFactory)
Introduce streamlined/improved factory based on Carman's work
Maven 2 build; Maven 2 HiveDoc plugin
More AOP interceptor stuff: ability to apply an interceptor to many
services (I've been calling these interceptor sets)
Code based builders / Java code to create service implementations (and
maybe other things) based on annotations and/or naming conventions.
Less XML.
Fix the relationship between the service factory and the service
lifecycle model to properly support event notifications to
non-singletons (i.e., threaded and pooled)
Some of these can be deferred to 1.3 if 1.2 happens fast enough
Annotations / 1.5 is important and controversial; that has to be
straightened out first.
On 1/16/06, Knut Wannheden <[EMAIL PROTECTED]> wrote:
Hi Howard,
I wish you a Happy New Year and congratulations for getting Tapestry
4.0 out the door!
Last year there were many very good ideas for the future of HiveMind.
But I don't think we ever quite decided which ones to go forward with.
I was thinking if we should do that now so users know what to expect
and developers have something to work on. Of course there are always
bugs one can work on :-)
I for myself haven't worked on HiveMind for quite some time now. I
worked on a new API for the RegistryBuilder for a while. I think that
might be something which we might want to discuss if we want to
implement support for Java annotations.
Then I also have a implementation for HIVEMIND-137 (new "default"
attribute for <attribute> element) in my workspace I don't know what
to do with. What's your opinion on this one?
Cheers,
--knut
--
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]
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.18/230 - Release Date: 2006. 01.
14.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
