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 yo
[EMAIL PROTECTED] wrote:
> On Thu, 6 Jun 2002, Christopher K. St. John wrote:
>
> > This sounds a bit like o.a.commons.modeler. (modeler
> > provides code to fill in MBean meta-data based on an external
> > xml file, see o.a.catalina.mbeans.mbeans-descriptors.xml)
> >
> > Is the magic jk co
On Thu, 6 Jun 2002, Christopher K. St. John wrote:
> This sounds a bit like o.a.commons.modeler. (modeler
> provides code to fill in MBean meta-data based on an external
> xml file, see o.a.catalina.mbeans.mbeans-descriptors.xml)
>
> Is the magic jk code related, a replacement, or just somet
[EMAIL PROTECTED] wrote:
>
> In case you didn't noticed, I checked in a small 'magic' util that
> turns Jk components into dynamic MBeans.
>
> It still doesn't support the 'descriptions' and the ability to
> fine tune the exposed attributes/methods, that will be added later
> ( and will probably
>As noted in the comments, the intention is to integrate it with the
>configuration layer, so we can make distinction between what is
>explicitely set by user and what is just a normal getter.
>
>Opinions ? Is it usefull or should I find something better to do ?
>BTW, it is trivial to enable all
