• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations

  • Subject: Re: JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
  • From: John Huss <email@hidden>
  • Date: Tue, 22 Apr 2014 22:03:38 -0500
I think the migrations are run in Application.finishInitialization, but I could be wrong.  So make sure you are calling super if you are overriding it.  You could at ERXApplication to find where it is called.  

The simple solution is to turn off "migrateAtStartup" and just add a call to run them yourself. 


On Tue, Apr 22, 2014 at 5:22 PM, Matthias Jakob <email@hidden> wrote:
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

 _______________________________________________
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
References: 
 >JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations (From: Matthias Jakob <email@hidden>)

  • Prev by Date: Re: "Manual" form submission with Ajax.framework
  • Next by Date: Sorry for the spam! [Re: Fwd: Abwesenheitsnachricht / out of office notice]
  • Previous by thread: JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
  • Next by thread: Re: JNDI JDBC entry in web.xml Servlet Deployment vs. Migrations
  • Index(es):
    • Date
    • Thread