Hi!
Pedro Mota wrote:
> I've been thinking about the easy way to separate the GUI from the
> data in jBoss classes. Here is one possible solution.
>
> Modify the class removing the code that uses awt, and then make a
> subclass (with same name + "GUI" for example) incorporating the
> GUI code.
This shouldn't be necessary. Since the GUI code is lazyloaded it
shouldn't be used on non-GUI usage.
However, I just got a support question with a stacktrace that hinted at
what causes the AWT runtime to be loaded: some plugins do not implement
XmlExternalizable, so EJX tries to use JavaBeans BeanInfo to get dynamic
info about it. This works well, BUT, the BeanInfo classes loads Icons,
which in turn needs the AWT Toolkit, which in turn uses the whole AWT
thing.
Sooo.. it *might* be possible to get this working simply by changing the
way the BeanInfo classes are loading Icons. If they lazyload this, then
that might make everything work.
I will try this, but since I don't have an AWT-sensitive environment
(i.e *nix /wo X-server) I won't be able to test it. I will try to figure
out whether it works anyway, but some *nix user will have to try it to
be sure that it works.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
