Hi Geeks

-----Original Message-----
From: Rickard �berg [mailto:[EMAIL PROTECTED]]
Sent: Friday, November 17, 2000 12:16 AM
To: jBoss Developer
Subject: Re: [jBoss-Dev] jBoss Administration GUI


Hi!

Andy \"Mad\" Schaefer wrote:
> The GUI will work this way:
> - when the plugin is loaded the user can enter the JNDI server and
> a query to look for the particular JMX Connectors
> - when the user selects then a JMX Connector the GUI will list all
> the available manageable resources (MBeans)
> - when the user selects a MBean the GUI will show an dynamic
> generated GUI to see and change the attributes and invoke methods
> (it will work similar to the HTML Adaptor)

Generated GUI is good, but we also need a way to use service specific
GUI's. Can you make some kind of mapping from ObjectName->GUI component,
so that if we have an explicit GUI we use that, otherwise use generated.
Down the road I think most GUI's should be explicit.

[Mad Andy]
Yes, I know but this is just the beginning. I suggest:
- Each MBean carries a version in his MBean interface
- the administration GUI will check this version
- then it will decide if there is a GUI representation working with this
  GUI and if not just using the generic one
- the jBoss service developer just has to enter the version in this MBean
  (hardcoded)
- the jBoss administration GUI developer then defines for which version
  his GUI will work (can be one number or a range) (defined in properties
file)
- if there are more than one GUIs able to work with the service the user
  has to pick one
- later on we have to decide what happens if there a GUIs written working
  with more than one service
The idea behind is to separate the server-side development from the
administration
GUI development that they do not depend on each other. Therefore when the
server-side developer improved a service the admin GUI developer has to
decide
if his/her GUI can work with the new version and when not then adjust the
existing one or create a new release.

At the moment Simon Bordet and I are improving EJX/AWT therefore that it
we can create attractive GUIs on top and make the life easier to develop
with.

I am discussing this for a while and now I want to start with a generic one
just to see how everything works together (server, JMX, JMX Connector, EJX
and EJX Plugin(s)).

Have fun - Mad Andy

/Rickard

-- 
Rickard �berg

Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com

Reply via email to