Jason van Zyl wrote: >>Here's the full URL: http://www.jconfig.org/ConfigurationServer.html >> >> > >Cool! I'll take a look and try to integrate it into what I'm making. > > Yeah, I think we are all on the same page now.
- Build a single archive - swizzle J2EE files that need to be changed for deployment, as part of the deployment process, not the build process - externalise as much configuration as possible As for a configuration server - that's a good idea (I was going to try using a directory server, as I had most of my config in JNDI to centralise the deployment profile to one file). Managing those servers (which could become a single point of failure for the app) might not be desired in some places though, so it's good to have a "push" alternative, where you centralise all the configuration still, but push it out onto a cluster of servers and change acording to the environment. Where does this all leave filtering? Seems like we should have it, and we develop some best practices and possibly deployment tools that demonstrate what we have here. Everyone agree? Anyone want to take a stab at a little doc? - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
