Ok, here are my interests:
short term:
- multiple service implementations, configuration and selection
- directory files for loading multiple modules from the classpath (discussed here some weeks ago)
- Simplifying configurations that hold service instances (also discussed as 'pushing an attribute value onto the rules stack)
long term:
- Manageability and Deployment
In my wildest dream I can add some meta data to my hivemind modules that
enables me to create automatically special deployment information.
One the one hand this information could be used as documentation
that tells the deployer (in terms of j2ee roles) which configuration
settings he must provide before deploying the (web) application (database servers,
pool and cache sizes, log settings, mailservers etc.). This would be a subset of the
documentation that can be generated with hivedoc.
One the other hand one could use the information to provide tool support
for the initial configuration and the runtime change of configuration data.
The latter one could be realized with jmx and a web interface (like the tomcat
administration app). Runtime configuration additionally could be supported by a
scripting language that changes the settings of a running application via jmx remote calls.
Imagine a shell script for changing the log level
to 'debug' for all nodes of a web application cluster.
Bye Achim Huegen
So ... what are people doing with HiveMind? It's back, it's free and I've been doing some work on
it. I've also been doing some planning for HiveMind on the Wiki.
I'm afraid that all the interruptions caused by the IP problem, and then by the infrastructure
delay, have hurt HiveMind. The community is failing to coalesce at the new home ... it's important
that the other HiveMind users and developers check in and start communicating about their needs.
I have plans for HiveMind in the immediate future:
- Hook into J2EE for declarative security on services via an interceptor
- Create a gateway into Spring, to allow managed Spring beans to appear as HiveMind services
- Interface with JMX: map JMX MBean interfaces to HiveMind services, and add a "performance"
interceptor that records method invocation data into other JMX beans
- Transaction interceptor
That's my immediate list ... what's your?
-- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Tapestry: Java Web Components Creator, HiveMind http://howardlewisship.com
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
