|
|
| Re: Resolve Proxies during linking phase [message #1312743 is a reply to message #1312400] |
Thu, 24 April 2014 13:22   |
|
I am afraid that resolving crossrefs during linking is not a good Idea
since you may run into a chicken egg problem. Using the URI of the proxy
and try to resolve against the resources ResourceSet may lead to cycles.
Anyway - why don't you use a postprocessor after linking has been done.
Cheers,
Holger
On 24.04.14 14:50, Norman Lenzner wrote:
> Hi,
>
> we defined a DSL that supports a "templating" mechanism like:
>
> TEMPLATE t
> ATTRIBUTE a1
> ATTRIBUTE a2
>
> ENTITY e1 FROM t
>
> ENTITY e2 FROM t
>
> During the linking phase, our linker copies the "ATTRIBUTE"-elements
> from the templates to the entities and the code generators work on a
> model that was modified this way.
> Now we have a problem, when template and entity are defined in different
> resources:
> Resource r1 contains
> TEMPLATE t
> ATTRIBUTE a1
> ATTRIBUTE a2
>
> Resource r2 contains
> ENTITY e1 FROM t
>
> When the linker processes r2 the template t is a proxy object and we
> have no idea how to resolve this proxy to copy the attributes.
> Is there any way to get the "ATTRIBUTE"-elements of t when linking r2?
>
> regards
> Norman
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.02487 seconds
] 
Search
Help
Register
Login
Home
