Hmmm... I'm not sure I follow you here, Rickard. Besides this,
you've said elsewhere that EJX just "knows" what plugins to load, so you
don't have to load things manually.
However, when I look at the code, the JBossFileManager loads
ejb-jar.xml and jboss.xml - and that's hardcoded. Then the
JawsFileManager loads ejb-jar.xml and jaws.xml - also hardcoded. The
JawsFileManager gets loaded by the JAWSPersistenceManager, which gets
loaded since its class is named explicitly in jboss.xml.
This does not seem automatic or "magical" to me - and EJX is not
loading things "dynamically". The container code is dynamically loading
JAWS based on an entry in another file, but all four files loaded are
hardcoded in the FileManager classes. (I won't even ask why ejb-jar.xml
is loaded twice!)
In the EJX GUI, you specifically tell it which plugin to use when
you open a file - you have to say "open as type [EJB-JAR | JBoss | JAWS]".
So here again, I'm not seeing EJX doing anything dynamic. Can you clarify
what you mean when you say EJX just "knows" what plugins to load and
"loads the right plugins dynamically"? It looks to me like it just does
what you tell it to - which is eminently reasonable, and the way the new
metadata behaves as well.
Thanks,
Aaron
On Sun, 9 Jul 2000, Rickard [iso-8859-1] �berg wrote:
> You stepped over the most important step here. The "if the beans used
> JAWS". This should not be done manually. When the structure is loaded
> the JAWS settings plugin should automatically be added as an aspect of
> the EJB *that uses JAWS*. The other beans should *not* have these
> aspects added. This is doable by changing the current code.
