success

     http://admc.com:8080/jmxhtml/jmx

Implemented according to the agreed-upon strategy.

It may or may not be possible to make this work with the sample
MBeans only on the server side, but that'll take some work.  For
now, I need the sample classes available to the web app and the
back end.  The war needs the classes, at the very least, to get
the class constructor signatures for the createMBean calls.  We
could get the signatures from the MBean which Simone spoke of
(the Sample MBean lister MBean).  But I don't know whether the
JVM needs access to the underlying MBean classes to work with
MBeanInfo objects, etc.  I'm sure that somebody on this list has
some insight into that.

The problem with the R.I. message showing up went away when I
specified a good URL.  Maybe under TC things somehow fall back
to the R.I. in .../common/lib when the jmx imp in my war fails
to recognize the URL (similar to how JDBC drivers each get an
opportunity to accept a given jdbc URL).

I still need to optimize the policy files for both standalone
and web-app demo sites.


My original purpose was to show off the mx4j HTTP Adaptor and
give the public access to live instances of the mx4j sample
MBeans.  It seems to me like this can be accomplished more
simply by running a HttpAdaptor under a security manager.  I
see no advantage to the 2-tier web app approach for this goal.

I could see it being worthwhile to provide a mx4j jmx management
war with the mx4j distro.  That would really differentiate mx4j
from R.I.  In this case, the demo site could be a demo for the
mx4j war file.  But I have no idea if this is desired.

Let me know what I should be working on.


-- 
Don't pray in my school, and I won't think in your church.
ICF:  703-934-3692       Cell:  703-944-9317


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click