JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
- Subject: JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
- From: Matthias Jakob <email@hidden>
- Date: Wed, 23 Apr 2014 00:22:21 +0200
Hi there!
I’ve got a problem with my web.xml JNDI JDBC entry in Servlet Deployment and migrations.
Using the web.xml entry
<resource-ref>
<description>MS SQL Server</description>
<res-ref-name>jdbc/TEST</res-ref-name>
<res-type>javax.sql.DataSource</res-type>
<res-auth>Container</res-auth>
<res-sharing-scope>Shareable</res-sharing-scope>
</resource-ref>
It works fine with an already created database and a „Properties" database config.
With an already created database and a switch from properties to JNDI JDBC all is fine ;-) (database operations are done ..)
But if I clean my DB and start form zero, no migration is done with JNDI/JDBC entry?
It’s an ERXApplication, the properties are right I think:
# Migrations
er.migration.migrateAtStartup=true
er.migration.createTablesIfNecessary=true
er.migration.modelNames=Test
er.extensions.migration.ERXMigration.useDatabaseSpecificMigrations=false
Test.InitialMigrationVersion=0
Test.MigrationClassPrefix=xx.xx.Test
JNDI JDBC is a must have, because of a large deployment environment, properties conf is not an option ;-(
What is wrong, what can I do to fix the problem?
Please help!
Matthias
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden