Nov 2nd, 2009, 08:53 AM
Design for overriding SQL statements at runtime
Can I run a design idea past the gurus in this forum?
We have a requirement to be able to change SQL statements used by Spring-configured Dao’s without requiring a redeployment of the war/ear. Currently, we use component-based Spring configuration, i.e., each “component” consists of a jar file and spring configuration file. We plan to change our DAO's to support injection of the SQL statements rather than hard-coding them in the java code.
To support changing the SQL without a restart, I am thinking of using the propertyOverrideConfigurer. This means the components could be self-configuring, but an override file in the classpath could override SQL statements in specific dao’s, as needed.
What are your thoughts on this approach? Are there better ways to accomplish this goal?