| Hello,
I'm using WO 5.4.1. I have a Wonder application with its own small EO model. Naturally I'm using ERPrototypes for this. Meanwhile, I have factored out a couple of models from an older, non-Wonder application into their own framework. These models use different prototypes, which I have factored out into another framework---these are just some prototypes I created myself.
During application start-up, the inevitable happens:
Jul 14 18:52:56 RM[54321] (ERXModelGroup.java:109) WARN er.extensions.ERXModelGroup - Clearing previous class descriptions Jul 14 18:52:56 RM[54321] (ERXModelGroup.java:778) WARN er.extensions.ERXModelGroup - The EOModel 'erprototypes' does not have a connection dictionary, providing an empty one Jul 14 18:52:57 RM[54321] (ERXModelGroup.java:228) WARN er.extensions.ERXModelGroup - The model 'Prototypes' (path: file:/Users/paulh/Projects/WebObjects/Eclipse/LSWOPrototypes/build/LSWOPrototypes.framework/Resources/Prototypes.eomodeld) has an entity name conflict with the entities ("EOJDBCPrototypes") already in the model group <EOModelGroup ( ( Recipient, file:/Users/paulh/Projects/WebObjects/Eclipse/RM/build/RM.woa/Contents/Resources/Recipient.eomodeld ), ( erprototypes, file:/Library/Frameworks/ERPrototypes.framework/Resources/erprototypes.eomodeld ) )>
Assume that I _can't_ re-write the old models against ERPrototypes (I probably could, but that's a bridge I'd rather cross later). Is it possible to (perhaps programmatically) declare prototypes model-by-model? That is, can I tell EOF to use ERPrototypes for the model in the Wonder application, and my own prototypes for the models in the older, non-Wonder framework?
(I have read the "Changing Prototypes in Code" section in Practical WebObjects, but, unless I'm mistaken, that's providing a strategy for changing entirely from one set of prototypes to another.)
|