> And the more I think about it, I suppose "ServerMetaData" really
> should be "ApplicationMetaData" since it refers to the group of beans
> loaded by one particular set of configuration files - normally, the beans
> in one JAR. But that's not quite the right name either. Any suggestions?
Yes that is the way it is in EJX now (each container has a set of properties
that are dynamically configured based on the contents of the jar).
> Rickard, would the change to non-static identification of
> applicable plugins resolve your issue, or is it something else?
There are many "static" things in the metadata (the EJB spec at least).
I think we should separate what is "EJB container metalevel information"
(the spec stuff) from the configuration of the container and the server for
each bean . Even though they are carried by the same media (xml files in
the jar) they CERTAINLY should not live in the same classes (not accessed
from teh same points not living in the same space etc etc). For example teh
plugin configuration is DEFINITELY a JMX layer thing and I would go towards
the "dynamicity" of EJX. BTW I am just talking run-time here not GUI and by
all accounts I think the gui should be separated cleanly. \
I say separate. MetaData the new package does EJB (where you would expose if
the beans are CMP or BMP rickard, trivial in jboss 1.0 already ;-), EJX is
configuration of the JMX container managed pieces of the Server (must be
bean based since the server has multiple personalities per bean today).
regards
marc
>
> Thanks,
> Aaron
>
>
>
