On Thu, 6 Jun 2002, Amy Roh wrote: > Maybe we can add for admin to handle dynamic user added components later too. > :-)
Well, my assumption was that the /admin uses JMX. There is no distinction between dynamic, standard or model mbeans from the user point of view, it's just a choice in how you instrument the code. All that's needed is a UI to reflect what can be configured in jk, using the mbean names and attributes we register ( right now domain=jk2, name=component name ). Am I missing something ? Sorry, didn't look very close to the admin impl. so far, I'm just playing with the mx4j default adapter ( and I can 'see' both tomcat and jk objects in the same way ) Costin -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
