• 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: Matthias Jakob <email@hidden>
  • Date: Thu, 24 Apr 2014 19:19:49 +0200

Hi David,


protected void migrationsWillRun(ERXMigrator migrator) {
// TODO Auto-generated method stub
super.migrationsWillRun(migrator);
System.out.println("-->migrationsWillRun<--");
}

Is never called, local or in the Appserver ??

If migration run or not …

Calling migration by hand is not a problem ?

er.migration.migrateAtStartup=false 

@Override
public void finishInitialization() {
// TODO Auto-generated method stub
super.finishInitialization();
try {
System.out.println("-->finishInitialization<--");
        migrator().log.setLevel(Level.DEBUG);
            migrator().migrateToLatest();
            System.out.println("-->finishInitialization<--");
        }
        catch (ERXMigrationFailedException e) {
            // It might be a missing plugin problem
            e.printStackTrace();
        }
}




Am 24.04.2014 um 15:18 schrieb David Avendasora <email@hidden>:


On Apr 24, 2014, at 9:16 AM, David Avendasora <email@hidden> wrote:

Override the migrationsWillRun method and stick a breakpoint on it. Let’s make sure that it is getting that far.

Umm… in your subclass of ERXApplication, in case that wasn’t clear… It probably was to you, but hey, Future Dave is going to come here at some point, and *that* guy is pathetic.

Sir Dave

—————————————————————————————
WebObjects - so easy that even Dave Avendasora can do it!™
—————————————————————————————
David Avendasora
Senior Software Abuser
Nekesto, Inc.







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

  • Prev by Date: Re: SQL Generation Issue
  • Next by Date: Re: [Wonder-disc] SQL Generation Issue
  • Previous by thread: Re: 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