jdbc configuration parameter in properties
Posted: Wed Aug 29, 2012 6:13 pm
I notice hibernate persistent configuration parameters are in a properties file, but jdbc configuration parameters are hard-coded in multiple xml files. This makes it's hard to change jdbc configuration, e.g. change default hsql to mysql. I would like to see these parameters are moved to a properties file. This also allow us to configure different data source for different environment.
I spent some time fixed it in v1 m1-5 and it works great for 3 different environments. But working on v2 m1-4, I encounter this issue again, and this time I have no clue what I do wrong. Please refer to this at viewtopic.php?f=11&t=676.
Another suggestion is to use mysql for demo. Most users will start with mysql. No one can do anything with the in-memory hsql database. Though it's for a demo, many may build their app on the top of the demo, or at least as a reference. Using mysql will save everyone some time. It says the reason chosing hsql is because it's lightweight. But if we reference it at run-time why this matters?
Thank you!
I spent some time fixed it in v1 m1-5 and it works great for 3 different environments. But working on v2 m1-4, I encounter this issue again, and this time I have no clue what I do wrong. Please refer to this at viewtopic.php?f=11&t=676.
Another suggestion is to use mysql for demo. Most users will start with mysql. No one can do anything with the in-memory hsql database. Though it's for a demo, many may build their app on the top of the demo, or at least as a reference. Using mysql will save everyone some time. It says the reason chosing hsql is because it's lightweight. But if we reference it at run-time why this matters?
Thank you!