|Re: Proxy resolval for EAttribute [message #660432 is a reply to message #660317]
||Fri, 18 March 2011 12:04
| Stefan Jurack
Registered: February 2010
Daniel and me intended to kind of eliminate remote references from a
transformation engine's perspective in order to perform transformations
on local models only while being embedded in a larger context.
However, we have found a proper way of dealing with this without the
need of introducing additional abnormal behavior to EMF models, as this
is rather a concern of the transformation engine than of EMF.
Thanks for your help anyway.
Am 17.03.2011 21:10, schrieb Ed Merks:
> Comments below.
> Daniel Strueber wrote:
>> Ed Merks wrote:
>>>> I try to utilize an EAttribute in terms of a remote reference, since
>>>> using an EReference is not suitable in my special case for several
>>> Those reasons are?
>> Most basically, I have a set of model instances that are
>> interconnected by remote EReferences, and I want to pass
>> them on to an external infrastructure that performs a
>> certain "for all" check on all EReferences, but is designed
>> to deal with local EReferences only. So my idea was to use
>> EAttributes to distinguish the remote from the local
>> references. I'm having different ideas for workarounds,
>> but none of them is really neat, so I thought of giving this
>> a try.
> Nothing you said convinces me that you can't just use the existing proxy
> mechanism. There are many interesting ways to specialize how proxies
> are resolve and it's not so difficult to process a model instance
> without resolving any proxies.
> Maybe if you explain in a little more detail I could suggest some ideas
> you might try.
>> So thanks to both of you!
Powered by FUDForum
. Page generated in 0.01797 seconds