All,
Sometimes situations arise where one is not quite sure whether to laugh
or cry. This is definitely one of them.
I looked into the "AWT being loaded" problem, which seemed to be caused
by the BeanInfo classes (thanks to Roman Porotnikov for a decent
stacktrace). I changed the code template that was used for the BeanInfo
classes to do lazyloading of Icons. It turns out that it was the eager
loading of the images used by the icons that was the culprit in this
story. Once I had changed the template and rebuilt all the BeanInfo
classes the AWT subsystem was not started (I checked with the
-verbose:class flag.. HUUUUUUUUUUUUGE difference).
As a result, jBoss should now be usable on *nix servers without any
X-system, and (... drumroll ...) as a direct consequence of NOT loading
AWT the startup is MUCH faster and jBoss as a whole require MUCH less
memory :-)
CVS has been updated with the new BeanInfo generator, and the binary has
been updated with the latest BeanInfo classes. Those who use CVS should
do a full rebuild to make sure everything is generated properly.
Enjoy.
Now, laugh or cry? *That*, my friends, is the question..
Rickard, ROTFL
ps. If some *nix user without X-server can confirm that this actually
works, that would be great. Thx.
pps. As a side-result, this removes the requirement to separate the GUI
from the EJX plugins. Hohum.
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
