Hi,
in the moment I'm in the process of a major refactoring.
The goal is support for plain java modules, like I
prototyped in the annocon library (http://annocon.sf.net) and
adapted here for hivemind:
http://wiki.apache.org/jakarta-hivemind/AnnotationSupport
First milestone and proof of concept was the extraction of
any xml related stuff from the core framework. Although
quite a lot of work it works out nicely and most unit tests
are working again.
To ease the annotation support I made two other major
changes:
1. I shifted the registry build process from a pull priniciple
to a more convenient push principle. Thats similar to what Knut
envisioned here:
http://wiki.apache.org/jakarta-hivemind/DescriptorApiRevampProposal
2. I extended the configuration point concept to a broader scope.
A configuration is no longer limited to a list as type, but it can
be any collection or pojo. Have a look at the StrutsModule
example at the wiki.
All that will result in two new modules:
hivemind-xml.jar and hivemind-annotations.jar.
The framework will offer just a plain java interface for the set up of
registries.
Do you think that's the way HiveMind should go?
In that case I would open up a Hivemind 2.0 branch and check in my stuff
in the next weeks and provide some more technical details.
Achim Huegen
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
