At 09:46 1/4/01 +0200, Leo Simons wrote: >> 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. kewl. >> 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. It is fine to use the binary version but in the long run we will have to find/implement our own or else suns lawyers won't allows us to describe Avalon as JMX enabled (legally). >> 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. excellent - me too ;) >> 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. sounds good. >> 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? Not sure what you mean? Do you want to add it in a new repository or can you just keep it in phoenix's repository for the moment? Cheers, Pete *-----------------------------------------------------* | "Faced with the choice between changing one's mind, | | and proving that there is no need to do so - almost | | everyone gets busy on the proof." | | - John Kenneth Galbraith | *-----------------------------------------------------* --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
