Re: Two EOModels in one project

This probably isn't very helpful, but it seems like you have to do  
such things about five times before they work – and when you have  
faith that they work, they seem to work first go after that. You  
should not have to edit plists (although I have done that in the  
past, but now seem to use EOModeler in the correct order).

Also, I assume that both models are in the one framework. If not,  
make sure that the first framework is updated and available to the  
second in /Library/Frameworks, or wherever you are building it to.

Ian

On 24/01/2006, at 11:42 AM, [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?
>
> Denise
> _______________________________________________
> WebObjects-dev mailing list
> [email protected]
> http://www.omnigroup.com/mailman/listinfo/webobjects-dev
>