I have found the following advice:
You have to manually copy any *.eomodeld directories into the
framework's
build/xxx.framework/resources directory.
But my EOModels were already there. To be sure, I did copy the EOmodels
from the file system to the above directory in eclipse but that didn't
work...
There is a bug report on this issue,
http://objectstyle.org/jira/secure/ViewIssue.jspa?key=WOL-100
but it states that the bug concerns Eclipse 3.0.0 and wolips 1.1.0.71
on Win2k. I am on the Mac, and using wolips 1.1.0.82 beta 3. I am
(still) concerned?
Other Ideas?
JPM.
Le 15 oct. 04, ā 08:30, Jean Pierre Malrieu a écrit :
> Hi,
>
> I have an application using a framework. The framework contains two
> EOModels. The application references the framework. Yet, when running
> the application, I receive the famous error:
>
> An object store for the entity "XXX" could not be found. Verify that
> the entity is defined in an EOModel, and that the model is installed
> properly.
>
> Eomodels are not loaded. I don't know if it is an Eclipse issue. This
> happened suddenly, I don"t know exactly why. Maybe because I save one
> of the EOmodels...
>
> I have made some research on this error, and found that it might have
> been the result of ProjectBuilder and Eclipse bugs, but these messages
> are pretty old, and the bugs should have been corrected by now, so I
> don't know what to do...
>
> JPM.
>
This archive was generated by hypermail 2.0.0 : Fri Oct 15 2004 - 03:44:54 EDT