At the End,
don’t leave dbConnectURLGLOBAL blank ;-) thats all ;-(
Matthias
Am 25.04.2014 um 01:47 schrieb Matthias Jakob ja...@ementals.de:
Hi David,
hi Andrew,
hi there,
after a remote debugging session I’ve found the problem (Remember I will use
a JNDI JDBC Datasource!):
In
Thank you David, John,
Tested and found out that the first deployment on a fresh server works fine
with migrations. Uninstall WAR Application, delete Tables, Install again -
start - no migrations are executed ;-(
Glassfish, Websphere same behavior ...
Why? Confused ;-(
Thank you,
Matthias
what is the deployment environment?
what database?
is the database on the same machine?
what do the logs of the database say? (can you increase the logging to verbose?)
at least then you would know if your app is trying to talk to the backend.
migrations can not create the database. it must exist
Hi Theodore,
thank you for your help!
- WebSphere or Glassfish its the same.
- Microsoft SQL Server
- Remote Server
- second start with deleted Tables - no connection on Startup!!?!?
- Only _dbupdater and my single demo Table was deleted … No Database Drop … its
already there ...
;-(
Its
Hi Matthaias,
Override the migrationsWillRun method and stick a breakpoint on it. Let’s make
sure that it is getting that far.
Something like:
@Override
protected void migrationsWillRun(ERXMigrator migrator) {
super.migrationsWillRun(migrator); — breakpoint here
On Apr 24, 2014, at 9:16 AM, David Avendasora webobje...@avendasora.com 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
Clear ;-) Sir! ;-)
Am 24.04.2014 um 15:18 schrieb David Avendasora webobje...@avendasora.com:
On Apr 24, 2014, at 9:16 AM, David Avendasora webobje...@avendasora.com
wrote:
Override the migrationsWillRun method and stick a breakpoint on it. Let’s
make sure that it is getting that far.
Are you restarting the app server or just uninstalling the war? You have
to restart the server I think.
On Thu, Apr 24, 2014 at 7:59 AM, Matthias Jakob ja...@ementals.de wrote:
Hi Theodore,
thank you for your help!
- WebSphere or Glassfish its the same.
- Microsoft SQL Server
- Remote
don’t think so. I do this all the time.
are you sure you are including all frameworks when you build your app? maybe
the sqlserver .jar isn’t where you think it is.
On Apr 24, 2014, at 10:22 AM, John Huss johnth...@gmail.com wrote:
Are you restarting the app server or just uninstalling the
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
Hi David,
hi Andrew,
hi there,
after a remote debugging session I’ve found the problem (Remember I will use a
JNDI JDBC Datasource!):
In ERXMigrator
protected boolean canMigrateModel(EOModel model) {
String adaptorName = model.adaptorName();
if
I may be incorrect, but I don’t think migrations have ever been able to
*create* a database. I think you have always needed the DB to exist first, then
migrations can create schemas, tables, constraints, etc.
It has been a long time since I tried to start from scratch, so it is entirely
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
descriptionMS SQL Server/description
res-ref-namejdbc/TEST/res-ref-name
res-typejavax.sql.DataSource/res-type
res-authContainer/res-auth
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
14 matches
Mail list logo
