Alright,to answer myself: By default the ERTaggable framework uses its ERTaggable model and the associated model config. You have to overwrite the model config in your Properties file using the dbConnect...GLOBAL keys.
H. Am 27.06.2008 um 18:35 schrieb Helmut Schottmüller:
Hi,I tried to use ERTaggable framework for one of my models. I am using the "magic" way with database migration. But when I start my app, the migration fails:un 27 18:23:17 WOSupportManager[5555] (ERXNSLogLog4jBridge.java:43) WARN NSLog - A fatal exception occurred: Failed to migrate model 'ERTaggable'. [2008-06-27 18:23:17 CEST] <main> er.extensions.migration.ERXMigrationFailedException: Failed to migrate model 'ERTaggable'. at er.extensions.migration.ERXMigrator.migrateToLatest(ERXMigrator.java: 185) at er .extensions .appserver.ERXApplication.finishInitialization(ERXApplication.java: 898)at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)at sun .reflect .NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun .reflect .DelegatingMethodAccessorImpl .invoke(DelegatingMethodAccessorImpl.java:25)at java.lang.reflect.Method.invoke(Method.java:585)at com .webobjects.foundation.NSSelector._safeInvokeMethod(NSSelector.java: 120) at com.webobjects.foundation.NSNotificationCenter $_Entry.invokeMethod(NSNotificationCenter.java:601) at com .webobjects .foundation .NSNotificationCenter.postNotification(NSNotificationCenter.java:545) at com .webobjects .foundation .NSNotificationCenter.postNotification(NSNotificationCenter.java:559)at com.webobjects.appserver.WOApplication.run(WOApplication.java:878)at er.extensions.appserver.ERXApplication.run(ERXApplication.java: 992) at com.webobjects.appserver.WOApplication.main(WOApplication.java: 324) at er.extensions.appserver.ERXApplication.main(ERXApplication.java: 535) at de .conscius .supportmanager.application.Application.main(Application.java:33) Caused by: com.webobjects.foundation.NSForwardException [java.lang.NullPointerException] null: Failed to create sql helper for the database with the product name 'null'. at er.extensions.jdbc.ERXSQLHelper.newSQLHelper(ERXSQLHelper.java: 1296) at er.extensions.jdbc.ERXSQLHelper.newSQLHelper(ERXSQLHelper.java: 1243) at er.extensions.jdbc.ERXSQLHelper.newSQLHelper(ERXSQLHelper.java: 1238) at er.extensions.jdbc.ERXSQLHelper.newSQLHelper(ERXSQLHelper.java: 1251) at er.extensions.migration.ERXMigrator.migrateToLatest(ERXMigrator.java: 172)... 14 more I am using latest wonder, WO 5.3.3I assume, that I can use the tag migration in ANY migration step, not only the first one, isn't it? Anyway, I removed my database and added it into the first migration step. Is it possible that the framework is not working with PostgreSQL databases?Or do I have to add a taggable attribute to my entity manually (or by using the migration)? I didn't do anything to my taggable entity. After reading the quick start I suppose that the migration step does all the necessary options for me.Regards, Helmut _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/helmut.schottmueller%40mac.com This email sent to [EMAIL PROTECTED]
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
