Keep in mind the password encoder doesn't store location information. The JDBC connection setting would remain the same unless you swap out the driver.xml file. So I don't think putting the driver in cayenne.xml helps.
mrg On Sun, Dec 13, 2009 at 3:45 PM, Andrus Adamchik <[email protected]> wrote: > Since I am rewriting the project load/save code, I am going to add one more > format change - move .driver.xml stuff into cayenne.xml. The original > motivation for a separate file was to allow users to swap it in different > deployment environments, e.g. to protect their production password. Now we > have the password encoder facility that does not require file swapping, and > most JEE environments are using JNDI anyways, so makes sense to reduce the > complexity, and store the <driver>..</driver> section right in cayenne.xml. > > Andrus >
