A clever use of and where the is in the ${dialect} file will
give some pretty reasonable flexability without the need to exploit any
bugs. I have recently posted a JIRA feature request precisely to help
address key generation aspect of the cross-DB compatability issue more
easily using propertie
I would try a structure like this:Set up your SqlMapConfig.xml file to load a properties file, and in that properties file specify the database dialect (i.e., dialect=mysql, or
dialect=oracle, etc...). Then, you can load the common sqlmaps from a common location, and the dialect specific ones usin
