"[EMAIL PROTECTED]" 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? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3861442#3861442 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3861442 ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
