Andreas Schaefer wrote:
> - Dynamic lookups and environment detection (as far as I know in AppCenter
> you have to configure your environment)
Jini will help with this.
> - Still have a repository or user preferences where the user can save its
> environment
> to limit the dynamic lookups
An XML-file. (so, the EJX plugin would be a file-handler for this
XML-file, but most of the GUI would not deal with the actual XML-file
but with managing the servers)
> - Limit the access protocol to JMX Connector(s)
> - Make it pluggable which means that the user can define which view he/she
> wants
> to use especially if there are different views for the same MBean (or group
> of MBeans)
> - Allow the system to detect upgrades on the (remote) MBeans and
> use more than one view for different version of the (remote) MBeans
> - SUPPORT for on-line help (like JavaHelp) (must also be pluggable)
> - sexy GUI layout but for most this is the responsibilty of the service GUI
> component
> coder
Agree.
> After the design I would like to start with the implementation ASAP for a
> small number
> of core MBeans with simple GUIs. Even when the support for security has to
> laid in
> the design and implemenation I will postpone the full implementation for
> later because
> for now jBoss is still beta except someone else is keen to do it.
Sounds like a plan.
Let me know what you need to understand EJX, and let's use that as a
foundation.
/Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
