|> - the client has to be written in Java
|
|Yes, but I'd prefer a servlet oriented one instad of a Swing one.
same here... I will try the taglib approach to simplify it :)
|> The server implementation of JBoss could look like:
|> - either JMX MBeans or EJBs implements the server-side administration
|> - are registered at the JNDI server
|> - delivers the service interfaces to the client and map the
|request to the
|> server-side components
|> - I would suggest RMI as a transport protocol
|
|So, like what we have now with the RMI connector then?
yes only we wouldn't have to support the code of the connector...
|> Why not JMX ?:
|> - I aggree with Marc that JMX is good when the client is not written in
|> Java but ugly when it is
|
|JMX syntax can be hidden with things like the org.jboss.util.MBeanProxy
|though.
ohh nice... thanks
|> - A good Admin. Console must be easy to use, fast and reliable and I
|> think this could only be achieved when the Client is written in Java
|
|So, no HTML then? Hm....
no no no, I agree with you there... just offer an API and taglibs for it...
marc
