Let me share my usage experience: We don't use driver.xml at all. Just some empty file. Usually there is one node and DataSource for this Node is overridden by our configuration. We can't just build-in it in cayenne.xml because data base configuration can various on different server deployments. I mean that when all database settings are strongly set in cayenne.xml (that is inside your JAR/WAR) you can't change it so easy.
I have some ideas about dynamic adding of DataNodes. Is it possible? Evgeny. -----Original Message----- From: Andrus Adamchik [mailto:aadamc...@apache.org] Sent: Sunday, December 13, 2009 11:45 PM To: dev@cayenne.apache.org Subject: XML file changes: dropping .driver.xml 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
