Not quite sure what you mean. A JSF bean has no restrictions, so you can make them JMX beans - either by implementing xxxMBean interfaces on them or by one of the dynamic MBean construction techniques.
So in other words, backing beans can be JMX-instrumented the exact same way any other javabean can be.
As far as using JSF to operate someone else's MBeans, you can code up any sort of JMX client UI you like. For a more general UI, it's probably better to just install mx4j and let its builtin web interface handle it than to go to all the trouble of reinventing the same basic interface in JSF.
Customer surveys are for companies who didn't pay proper attention to begin with.
Joined: Jul 02, 2001
Hi Tim! I was hoping to use JSF as GUI for managing other mbeans. I was thinking of having a generic framework (which incorporates rich display, security and notifications) for this.
Were you referring to using MX4J's HttpAdaptor instead? I am relatively new to JMX so I'm not sure if I can customize HttpAdaptor to give our users a richer web experience.
Anyway, would you know how MX4J compare to Sun's JMDK?