Hey
Andreas Schaefer wrote:
> It's me again with my favorite topic EJX. After investigation EJX
> I found it a quite well, but bare bone tools (with EJX I also include
> Rickard's AWT).
Excellent! :-)
> Things I think we should address now:
> - Add EJX/AWT into CVS and add it to the jBoss build.xml to
> build it after changing the code.
It's already there in the "ejx" module. The EJX plugins that are jBoss
specific are in jBoss and are indeed compiled upon changes. The AWT
package needs to be added too though (if this is desired that is.
probably).
> - Not all data must come from a file therefore I would suggest that
> EJX doesn't use a file but an URL. This means the FileManager/
> FileManagerFactory should be renamed to ResourceManager/
> ResourceManagerFactory and support URL instead of File. Then
> an appropriate protocol handler (have a look at JDC for an tutorial
> on this topic) which can load and save data to any source/destination
> you like (web, JNDI, JMX Connector, CVS etc.).
Excellent idea. More complex, but should work well for standard case
(i.e. file usage).
> - Create a tool which allows the EJX plugin to define a GUI on the
> fly (like the information from the MBean see also the HTML-Adaptor
> on port 8082)
Part of this is already available in the EJBench plugin which creates a
GUI on the fly from EJBHome and EJBRemote objects (i.e. one can lookup
and invoke the methods in these objects).
> - Extend EJX to support JavaHelp, dynamically change the EJX-Menu,
> selection bar on the left hand side like in M$ Management Console
> (you would see a list of available plugins, within a plugin you see the
> instances you run and within them you could see items defined by
> the EJX-plugin).
+1.
> - Extend AWT to support more advanced GUI elements (at the
> moment I am not quite sure what is supported but I will delve into it.
> It would be also interesting if we can create a properties file telling
> the AWT to display a particular GUI element for a particular type
> (own text field instead of the default JTextField).
The GenericCustomizer uses the JavaBeans API extensively, so just make a
new PropertyEditor for each type of editor you want. More info on is in
the JavaBeans API spec.
> That's it for now but let me say something personal now and please
> don't take it to hard but I like to say something instead of carring
> unpleasant feelings around:
Always a good idea.
> Even when Marc said that we (the people) are here to carry out
> the ideas and prototyps of Rickard I think it is the responsibilty and
> task to support a handing over when Rickard likes to go on and hunt
> new ideas ESPECIALLY when he urge us to use his tools.
I agree.
> I only
> got a response from Rickard when I questioned EJX but when I
> asked for support: nada, nothing, nichts, niet (I don't know the
> swedish word for nothing).
I know, and I truly apologize for the silence. I've been *really*
"out-of-phase" lately (and doing stuff like the EJBDoclet I can do
pretty much in my sleep, so its not an indicator I'm afraid), and you're
not the only one who has been neglected (apologies to Simone, Andy, and
Marc seems timely). I'm recovering now, and will soon get on a flight to
the states and will bring all your stuff with me and will respond
properly as soon as I can.
> I would prefer spending my time on designing a JMX agent or
> designing a sexy GUI instead of hunting down EJX/AWT by
> myself. It's not only Rickard who can create a great design and
> brings in good ideas but to keep all other busy is also a way to
> keep him ahead of all others (I don't say that's Rickard intention but
> it is the way I feel).
Considering the non-help from me lately, I completely understand and
sympathize with that view.
> I commited myself to use EJX for the jBoss administration GUI because
> it is simple, small and already part of jBoss but I think we have to
> put a lot of effort into it to make it suitable as a jBoss administration
> GUI because this is what the users see and that's important.
And I really commend you for the effort you have put in there.
very best regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com