Broadleaf Commerce Discussion Forums

So, I'm trying to figure out switching between environments
http://docs.broadleafcommerce.org/core/current/appendix/runtime-environment-configuration
(staging-shared.properties vs development-shared.properties)

What I don't understand is how this can support different DB environments since there is only one jetty-env.xml per site per environment.

So if I want to start switching from HSQL to MySQL, I have to swap between different jetty-env.xml files to switch between the two DB environments?

Those runtime properties are not designed for properties at the container level, those are really just defined for the application level. Container-specific properties (like the JNDI database) would yes, be set at a unique jetty-env.xml file.

If you're not really using a standalone container when you deploy to other environments (e.g. if you're using a PaaS like Heroku) then you could move the JNDI datasource defined in the servlet container (Jetty) to just use a Spring datasource like this:



You would replace the bean entries that you find in applicationContext-datasource.xml with those. Then you could define 'database.driver', 'database.username' etc in your different environment properties files and it would work as you expected. This of course would require you to commit database usernames and passwords into your application to use them like that.

Thank you. I think I'll just switch between jetty-env.xml files if I need to. Hopefully I can switch over to MySQL permanently w/o issue