> 1 - get Enhydra running, compare jmx impl to reference impl
Enhydra lacks support for some jmx features. I've decided to
use the RI for development.
> 3 - look into license issues (I don't expect difficulties)
there are none. Both enhydra (in source form or any other way)
and the RI (though we can only distribute in in binary form)
can be easily used with the apache license.
> 4 - redesign kernel to prepare for jmx (especially Main.class, probably)
see my other e-mail.
> 5 - use dynamic MBeans/model MBeans/std mbeans/custom solution to
> implement Phoenix's services as MBeans.
I think dynamic MBeans are the best idea. I want to create a default
dynamic MBeanInfo that calls all of the avalon lifecycle methods.
This should be located in org.apache.phoenix.engine.jmx.
> 6 - write custom adapter (avalon-based using RMI, probably)
there are a few pointers on an RMI adapter in the spec. It is likely
that a feature version will hammer this out further. So an RMI adapter
is probably the way to go.
> 8 - create our own jmx impl
I'm using org.apache.jmx right now for simple wrappers around sun's
RI, allowing for easy swapping of implementations. Can someone set
up the repository so I can commit this?
greetz,
LSD
<java:sig>
About LSD = new PersonalInfo();
LSD.name("Leo Simons");
LSD.email("[EMAIL PROTECTED]");
LSD.URL( [
http://www.leosimons.com, // personal website
http://www.atfantasy.com, // fantasy RPG portal
http://www.the-sign.nl // web-design company
] );
LSD.quote("Buh!");
email.setSig((String)LSD);
</java:sig>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
