|Re: Problem with Cross-Referencing and ProxyURIs [message #1752240 is a reply to message #1752236]
||Fri, 20 January 2017 08:57
|| Sven Efftinge
Registered: January 2016
The uri you are looking at is a "lazy URI" from Xtext. After parsing xtext installs proxies with uri's that contain all the needed information to, at a later point, resolve the link.|
So it points to itself (the context), the EReference and the node (the text) of the cross reference.
It's not quite clear what the issue is that you have, but if you want to have the proxy resolved, you need to make sure you navigate the getter of the reference or call EcoreUtil.resolve.
If that still returns a proxy with the mentioned URI it means that it couldn't be resolved. I.e. the scoping didn't return an element.
Note that, the scope can be called differently from content assist and during linking, because the model might not be fully parseable so that the context might be different. Xtext tries to use the best context object it gets.
TypeFox - Support And Consulting For Xtext
[Updated on: Fri, 20 January 2017 08:59]
Report message to a moderator
Powered by FUDForum
. Page generated in 0.09580 seconds