Hi! My app is downloadable. People can install into any number of enterprise or personal environments. I bundle Tomcat, MySql drivers, etc. When you start it up there's a wizard that allows you to configure your system. In this context, even things that are generally configured statically must be dynamic... database connection parameters, cache multicast ip's, upload directories, email server locations, etc.
I certainly agree that it's a lot easier for me to ask the user to edit an XML file, but it's easier for the user to answer a set of easy on-screen questions (with recommended default values) and have me take care of the back-end config (and validating what values they choose). In this case, I'll likely make the following user-configurable via a UI: - whether or not clustered caching is on - multicast ip address, if on - max number of objects in the cache So, when the API's available, I opt to give the user simple control over it instead of hard-coding what works for me today. Generally saves me a lot of re-coding down the line when that one crazy user needs something special. Best, Joe View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3900537#3900537 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3900537 ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
