Re: Two EOModels in one project

Actually, you only have to have Xcode open for WOB ... EOModeler  
works fine w/o (including multi-model/multi-framework  
configuration).  I have one open right now :)

ms

On Jan 24, 2006, at 9:25 AM, Marc Respass wrote:

> If you're using Eclipse, you have to open the xcode project to get  
> the tools (eom, wob) to work. Open the xcode project that WOLips  
> provides. If you're using WOLips 1.x then you may want to get  
> version 2 which is not final but 2.0.0.86 has been stable for me  
> for a long time (http://www.mdimension.com/~wolips/). Install  
> instructions are here (http://objectstyle.org/confluence/display/ 
> WOL/Home). In the days, EOModeler did work just as the docs  
> describe. I haven't tried it in the current release of WO. If  
> you're using WO 5.2, you can still use the latest XCode and the  
> tools. Where the WebObjects.mpkg is is a Packages folder. Just  
> install the Developer tools manually without anything else. They  
> require supporting frameworks so you can't drag install them.
>
> Hope this helps
> Marc
>
> On Tuesday, January 24, 2006, at 02:59AM, Geoff Hopson  
> <[email protected]> wrote:
>
> 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...
> 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

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