-
15. Re: Configuring a container for POJOs
"adrian@jboss.org" wrote:
Under no circumstances should the micro container require XML.
XML is one option for configuring the server. All the XML parsing should do
is construct kernel metadata objects. It should not be attempting to construct the
real objects as dependencies will not be satisfied at this stage, e.g. classloading
dependencies.
Potentially off topic, but....
If another option was used for configuring the server, e.g. a web-based Administration Console creating kernel metadata objects, would we want to be concerned about keeping other configurations up to date? For example, enabling an update to the XML file after the kernel metadata was changed via the Admin Console? -
16. Re: Configuring a container for POJOs
Correct you are offtopic.
Versioned/Persistence are planned see the comments about Profile in the design/JIRA.
These are only possible where there is some MetaData repository.
Adhoc programmatic deployment cannot persist to something that does not exist.
e.g. If you want to create a new DataSource, this could be done programmatically
but unless it is stored back to the profile (either xml or some other store) it won't
know it exists on a restart.
Better is to modify the profile using a programmatic interface.
This also has the advantage that it is versioned and so can be reverted to last known
good state if you don't like the changes.