The template mechanism seems too disconnected from the current jmx notions. Effectively this is a custom ant build process embedded into jboss and has poor integration with future notions of heirarchical metadata, is coupled tightly to jboss dist layouts and service interface versions, and is too tightly coupled to the existing file system based configuration. I thought we had discussed an abstraction like a deployment service and configuration service that would allow for a more natural view of the server configuration, peristence and versioning as another aspect of the server.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3852103#3852103 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3852103 ------------------------------------------------------- This SF.net email is sponsored by: IT Product Guide on ITManagersJournal Use IT products in your business? Tell us what you think of them. Give us Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more http://productguide.itmanagersjournal.com/guidepromo.tmpl _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
