I'm not sure if using erprototype (or prototypes in general) work even
halfway reliably on their own. We fix quite a few issues in load order
of models, merging and others... Also, erprototypes mainly exists for
the examples, BugTracker and ERCore. I use it occasionally, but mostly
add a EOMyModelPrototypes in the actual model.
Cheers, Anjo
Am 12.01.2009 um 20:46 schrieb Stamenkovic Florijan:
> Hi all,
>
>
> Here's the situation. I've copied erprototypes.eomodeld to the
> Resources folder of my model framework. I can't simply link to
> ERPrototypes.framework coz it wants to have other parts of Wonder
> then, too. So, this works. The framework is built with the latest
> hotness, and in the dist's Resources folder I see both models, the
> prototypes, and my actual model. In Eclipse's entity modeler I have
> no problems, the prototypes are detected and used.
>
> Now, I have an app that links to my model framework, and embeds it.
> In Eclipse, I can run the app, all is fine etc. However, copying of
> the dist product to a remote server caused some exceptions, so when
> I did some checking, I saw that the dist of my app embedded my model
> framework, but the framework's Resources folder contains only my
> model, and not erprototypes.eomodeld. Which explains why the app
> crashes at startup, but makes me wonder why didn't the prototypes
> model get copied?
>
> So, is this a bug in the build, or am I not allowed to have multiple
> eomodels in the same framework? Or something else???
>
> F
>
> p.s. - I guess the easy workaround is isolating the prototypes model
> into my own framework, essentially make an ERPrototypes.framework
> that does not have dependencies on the rest of wonder. Still, I
> thought I should be able to do it the way I did...
This archive was generated by hypermail 2.0.0 : Tue Jan 13 2009 - 06:29:13 EST