Hi,
It works like a charm.
Thank you!
Le 1 août 06 à 04:13, Mike Schrag a écrit :
> I just checked in a stopgap for this. There is new .eomodelgroup
> file and editor that looks curiously exactly like the .eogen editor
> (they requirements are kind of similar and it was convenient to
> just steal and hack the editor). When you create an eomodelgroup
> file, you essentially manually select the models that will appear
> in the EOModelGroup (vs Entity Modeler hunting for them for you).
> The first model defined in the Models section is that one that will
> actually open inside Entity Modeler when you "Open With..." an
> eomodelgroup file with Entity Modeler. It's sort of a lame fix,
> but it should work out for you. So you would create something like
> a YourModelFrontBase.eomodelgroup and YourModelOracle.eomodelgroup
> and each one would define the dependencies for your model to load
> properly with unique models and entities into Entity Modeler. Long
> term, this should get a nicer editor, but it should do for now.
>
> ms
>
> On Jul 31, 2006, at 8:00 AM, Stéphan Mertz wrote:
>
>> Mike,
>>
>> The models are not in a directory used by NSBundles.
>> I dynamically load the right model for the specific database,
>> during the init of the WO app.
>> My solution is not very academic, but it works.
>>
>> sm
>>
>> Le 31 juil. 06 à 13:45, Mike Schrag a écrit :
>>
>>> How do you actually use these models at runtime without totally
>>> confusing your WO app? The rules of NSBundle are what we are
>>> based on, which is "load all the models we find," hence the
>>> explosion you're seeing (though I really expected it to rename
>>> duplicate entity names -- also not desirable for you, but I'll
>>> have to check on that one).
>>>
>>> ms
>>>
>>> On Jul 31, 2006, at 5:07 AM, Stéphan Mertz wrote:
>>>
>>>> Hi,
>>>>
>>>> I have in my project, different version of the same Model, one
>>>> for each database I use.
>>>> If I try to open a model, I have this exception:
>>>> org.eclipse.core.runtime.CoreException: Failed to load model in
>>>> F/JavaResUrgencesEO/models/ResUrgences_MySQL.eomodeld.
>>>> at
>>>> org.objectstyle.wolips.eomodeler.model.EclipseEOModelGroupFactory
>>>> $ModelVisitor.visit(EclipseEOModelGroupFactory.java:163)
>>>> [...]
>>>> org.eclipse.core.runtime.CoreException[0]:
>>>> org.objectstyle.wolips.eomodeler.model.DuplicateEntityNameException
>>>> : There is more than one entity named 'Acte' in this model group.
>>>> at
>>>> org.objectstyle.wolips.eomodeler.model.EOModel._checkForDuplicateEn
>>>> tityName(EOModel.java:250)
>>>> at org.objectstyle.wolips.eomodeler.model.EOModel.addEntity
>>>> (EOModel.java:278)
>>>> [...]
>>>>
>>>> Is there a way to manage this type of configuration?
>>>>
>>>> Sincerely,
>>>>
>>>> Stéphan Mertz
>>>>
>>>
>>
>
This archive was generated by hypermail 2.0.0 : Wed Aug 02 2006 - 03:46:16 EDT