I was thinking about making HiveMind simpler and more generic. My thoughts went into the direction of "dropping" the configurations as they are today. Why not viewing configuration/contributions as services implementing some data interface, i.e. generalizing services and configurations. >From a Pojos point of view there is no difference, it has constructor parameters or setter parameter being of some interface. List is also an interface of a component that could have been implemented by a service. Maybe it is possible to write a nice ServiceImplementationFactory that does things like converting a contribution into a Map!?
Just a few thoughts for the weekend to share with you! Stefan compeople AG Untermainanlage 8 60329 Frankfurt fon: +49 (69) 272218 - 0 fax: +49 (69) 272218 - 22 email: [EMAIL PROTECTED] home: www.compeople.de --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
