Found this original WO doc to share and hope it helps. Not sure if this still
hold water after integrating with Wonder:
"When resolving a prototype name, Enterprise Objects Framework looks for
prototypes in EO<adaptor-name>Prototypes, then in EOPrototypes, and finally in
the adaptor for your model. This search path allows you to override the
prototypes provided by each adaptor. Furthermore, if you don't want to use the
adaptor-defined prototypes at all, you can hide them. Create an entity named
EOPrototypesToHide. For each prototype you want to hide, create an attribute
with that name; you don't need to specify other attribute properties."
Cheers
Cheong Hee
----- Original Message -----
From: Ângelo Andrade Cirino
To: Cheong Hee (Gmail)
Cc: Chuck Hill ; webobjects-dev@lists.apple.com
Sent: Wednesday, December 19, 2012 1:06 AM
Subject: Re: Migrations problem with FrontBase
Hi guys,
For a reason beyond my skills, the application seems to be indeed using the
MySQL prototypes instead of FrontBase's to create the _dbupdater table. My
model surely has the FrontBase prototypes selected, but this seems not to
influence the prototypes choice by ERXMigrator or ERXJDBCMigrationLock. So my
solution was to create the _dbupdater table by hand and populate it with the
models I use. After this intervention the migrations worked again.
But the question remains, from where does ERXMigrator take the prototypes
information?
Cheers,
Angelo
2012/12/18 Cheong Hee (Gmail) <chn...@gmail.com>
I think you are still picking up MySQL prototype file rather FrontBase
prototype file. INT is external type for intNumber in MySQL prototype file.
The correct external type for FrontBase prototype file is INTEGER.
You may check the prototype selection in your database configuration.
Somehow you are still picking up the MySQL prototype file.
Cheers
Cheong Hee
----- Original Message -----
From: Ângelo Andrade Cirino
To: Chuck Hill
Cc: webobjects-dev@lists.apple.com
Sent: Monday, December 17, 2012 11:07 PM
Subject: Re: Migrations problem with FrontBase
Hi Chuck,
The ERPrototypes and FrontBasePlugin libraries are correctly set up in
the class path. The FrontBase related JARS and frameworks are set up in the
system class path. In the model file the FrontBase prototypes were selected.
Trying to isolate the problem to study a solution, I stripped down the
migrations file generated, leaving only one entity and only the string-based
attributes. After this I got the following error:
Dez 17 12:45:04 AdministraAgencias1.0[60001] INFO
er.transaction.adaptor.ConnectionAnalyzer - JDBC connection successful!
Dez 17 12:45:04 AdministraAgencias1.0[60001] ERROR
er.extensions.appserver.ERXApplication - AdministraAgencias1.0 failed to start.
JDBCAdaptorException: Unable to find type information for external type
'INT' in attribute 'updateLock' of entity '_dbupdater'. Check spelling and
capitalization.
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseExpression.columnTypeStringForAttribute(_FrontBasePlugIn.java:1187)
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseExpression.addCreateClauseForAttribute(_FrontBasePlugIn.java:1095)
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseSynchronizationFactory.addCreateClauseForAttribute(_FrontBasePlugIn.java:905)
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseSynchronizationFactory.createTableStatementsForEntityGroup(_FrontBasePlugIn.java:845)
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseSynchronizationFactory.createTableStatementsForEntityGroups(_FrontBasePlugIn.java:809)
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseSynchronizationFactory.schemaCreationStatementsForEntities(_FrontBasePlugIn.java:640)
at
com.webobjects.jdbcadaptor._FrontBasePlugIn$FrontbaseSynchronizationFactory.schemaCreationScriptForEntities(_FrontBasePlugIn.java:606)
at
er.extensions.jdbc.ERXSQLHelper.createSchemaSQLForEntitiesWithOptions(ERXSQLHelper.java:286)
at
er.extensions.migration.ERXJDBCMigrationLock.dbUpdaterCreateStatement(ERXJDBCMigrationLock.java:370)
at
er.extensions.migration.ERXJDBCMigrationLock._tryLock(ERXJDBCMigrationLock.java:148)
at
er.extensions.migration.ERXJDBCMigrationLock.tryLock(ERXJDBCMigrationLock.java:69)
at
er.extensions.migration.ERXMigrator$ERXMigrationAction.doPerform(ERXMigrator.java:451)
at
er.extensions.eof.ERXEOAccessUtilities$ChannelAction.perform(ERXEOAccessUtilities.java:1502)
at
er.extensions.migration.ERXMigrator.migrateToLatest(ERXMigrator.java:201)
at
er.extensions.appserver.ERXApplication.finishInitialization(ERXApplication.java:1294)
... skipped 13 stack elements
Any clues? Adding a little more information, the migrations and
application worked well with MySQL, but a problem with a circular relationship
convinced me to switch to FrontBase, when I faced the error above for the first
time. Well, to say the truth, I had a problem with the connection dictionary
password, but was able to solve it specifying the dbpasswd and upasswd
properties.
Angelo
Em 17/12/2012, às 00:42, Chuck Hill escreveu:
It sounds like the wrong prototypes are being used to generate the
migration Java.
--------------------------------------------------------------------------
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/chng34%40gmail.com
This email sent to chn...@gmail.com
--
Ângelo Andrade Cirino
aacir...@gmail.com
31-3494-8642
31-9303-0695
MSN aacir...@hotmail.com
Skype aacirino
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
