Eclipse Community Forums: TMF (Xtext) » Diagnosing ambiguous references

Help

Home

Home » Modeling » TMF (Xtext) » Diagnosing ambiguous references

Show: Today's Messages :: Show Polls :: Message Navigator

Diagnosing ambiguous references [message #776077]

Sat, 07 January 2012 11:28

Ed Willink

Messages: 7655
Registered: July 2009

Senior Member

Hi

The invocation of getLinkingService().getLinkedObjects within
LazyLinkingResource.getEObject() does not appear to support ambiguities
completely.

getEObject() may return a list of ambiguous alternatives but the
subsequent testing then throws an untidy IllegalStateException, when it
would be much more user friendly to return some form of "Ambiguous
reference" diagnostic.

Is there a way to workaround this limitation other than my current
approach just returns an empty list and so reports an "Unresolved ..."
whenever the true problem is "Multiply resolved ...."

Regards

Ed Willink

Report message to a moderator