I ended up adding the models to the application itself, and copying
then to the build/xxx.woa/Contents/Resources folder. My models are now
loading. But then I have to maintain several copies of then, one in the
framework, an one in the application. Not very convenient. Each time I
modify the models, do I have to manually copy them to the
build/xxx.woa/Contents/Resources folder?
JP.
Le 16 oct. 04, ā 18:22, Jean Pierre Malrieu a écrit :
> It's an upgrade from 1.1.0.70.
> When I add a model (by dragging from file system) to a framework, or
> application, do I have to "Include as resource" it?
>
> Jean Pierre.
>
> Le 16 oct. 04, ā 13:51, Ulrich Köster a écrit :
>
>> Hi Jean Pierre,
>>
>> is it a vanilla install of WOLips or an upgrade from another beta?
>>
>> Ulrich
>>
>> Am 15.10.2004 um 09:44 schrieb Jean Pierre Malrieu:
>>
>>> 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 : Sat Oct 16 2004 - 12:36:14 EDT