> So, the process to follow as I envision it would be:
>
> 1 - get Enhydra running, compare jmx impl to reference impl
> 2 - if we choose Enhydra, extract jmx code from it
> 3 - look into license issues (I don't expect difficulties)
> 4 - redesign kernel to prepare for jmx (especially Main.class, probably)
> 5 - use dynamic MBeans/model MBeans/std mbeans/custom solution to
> implement Phoenix's services as MBeans.
> 6 - write custom adapter (avalon-based using RMI, probably)
> 7 - write management app to talk to adapter (either java program or
> servlet-based)
> long-term:
> 8 - create our own jmx impl
> 9 - design authentication scheme for allowing access to adapter
I think it would be useful finisih things in layers.
Layers could be
a) Get the reconfiguration working via JMX interfaces.
b) Get Notification interfaces working. This is really important, beacause a
server framework needs to tell the right people about the state.
c) do integration of JMX with SNMP, WBEM etc. Whatever the adminstrators
need to manage the server.
d) Get the class reloading , kernel design issues right.
I think (a), (b), (c) are really important and in some way add to but not
require dramatic changes to the Avalon Kernel. (d) would require maximum
changes, but I think a good server solution would have redundancy, so it
should be ok to provide a good stable server solution without even doing
(d). On the other hand (d) seems interesting.
I don't know much of the kernel, the changes I did in earlier Avalon
framework were pre-phoenix.
My impression has been that Enhydra provides a lot of things - Reloading,
SNMP, JNDI namespace, logging etc. It is and Avalon competitor. I had tried
to the some of the above things, like running Enhydra, trying to make sense
out of their JMX stuff etc, but could not get enough cycles in it. At one
point I found some documentaion on how they do class reloading. Apparently
they have a hierarchy of class loaders, and a delegated class reloading
mechanism. Will try to look it up.
Sorry about the delay in response, got sucked into something and poof goes
the weekend. :-(
Harmeet
>
> I'd like any and all suggestions for #4-7, as well as help actually
> implementing all this stuff. Harmeet, I'm guessing you'd be most
> productive helping out with the kernel design. So draw up some
> schematics, if you want ;-)
> Oh, comments on the route to follow welcome as well =)
>
> g'night, all!
>
> 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>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
