I agree with your disagreement. A JPA provider runtime can be more flexibly configured at runtime via different means than to have all the details supplied via *hard-coded* persistence.xml. One mechanics, as you have mentioned, can be via JNDI registered data source. The other (non-exclusive of the former) could be to pass properties in a Map during EntityManagerFactory (Persistence.createEntityManagereFactory(String,Map) bootstrap method. May be you can find an elegant solution by identifying the database type *before* the bootstrap and pass DBDictonary or other connection parameters (URL etc.) accordingly.
----- Pinaki Poddar Chair, Apache OpenJPA Project -- View this message in context: http://openjpa.208410.n2.nabble.com/changing-specific-openjpa-jdbc-DBDictionary-tp7143394p7147038.html Sent from the OpenJPA Users mailing list archive at Nabble.com.
