Re: Two EOModels in one project

I always end up having problems with this. And I always end up opening the
ModelB.eomodeld folder and editing the appropriate plist, manually adding
the name of the entity in the ModelA.eomodeld to the relationship definied
in the plist. Then, when I open the ModelB.eomodeld in EOMuddler and access
my entity, it prompts me to find ModelA.eomodeld. And, as if by magic, the
popup in the inspector is populated with ModelA and ModelB.

I use Eclipse/WOLips as opposed to XCode, so YMMV...

Geoff


On 24/01/06, Denise Howard <[email protected]> wrote:
>
>
> On Jan 23, 2006, at 8:29 PM, Guido Neitzer wrote:
>
> > On 24.01.2006, at 1:42 Uhr, [email protected] wrote:
> >
> >> I'm adding to an existing framework with an EOModel.  Call this
> >> model A.  I'm creating some new entities which we'd like to keep
> >> in a separate EOModel.  Call this model B.  Some model B entities
> >> need to have relationships to entities in model A.  According to
> >> the EOModeler help docs, this is as simple as adding model B to
> >> the framework project, and choosing between the two models in the
> >> relationship inspector.  However, when I create a new relationship
> >> in model B, the Model popup list shows only model B.  How do I get
> >> it to also offer model A?
> >
> > In the Inspector, above the list of entities, should be a popup
> > window where you can choose another model. Perhaps you have to quit
> > EOModeler and start it again.
>
> Yes, I know about the popup list--I mentioned it above.  I've tried
> several combinations of quitting EOModeler, closing models, quitting
> Xcode and closing the framework project.
>
> Denise
>
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev