At the moment, the Template Manager reads the template details from a fixed list of xml index files.
It's not particularly easy to add new templates or sets of templates. I wonder whether the Template Manager should use a process of discovery more like the way plugins are detected? For example, rather than specifiying a list of files, it could work from a list of directories. It would be quite expensive to scan the JMX files themselves, but it should be quick enough to scan any index xml files it finds. If the manager could also load templates relative to the index file, it would be possible to drop a set of files + index anywhere in the templates directory tree and have them picked up. The Manager should probably not scan every time, but it would be easy enough to add a Reload button to the dialog. I don't think we need to implement this all immediately - it could wait for the next release. Could even consider scanning zip/jar files containing templates plus their index. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
