|Re: [Xtext 2.1] What about scoping and typesystem? [message #753900 is a reply to message #753835]
||Sun, 30 October 2011 12:33
| Sebastian Zarnekow
Registered: July 2009
it's most likely the binding to the ITypeArgumentContextHelper which is
causing the confusion. It think the easiest way is to fix this is to
bind the XbaseTypeProvider class to your subtype in your runtime module.
Both the ITypeProvider and ITypeArgumentContextHelper are bound the the
XbaseTypeProvider by default. If your redefine the XbaseTypeProvider to
YourTypeProvider, both interfaces will use the same concrete
Hope that helps,
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
On 29.10.11 10:36, Ingo Meyer wrote:
> Yes and in some cases it will call my method, but in others not.
> When debugging I see it is not my TypeProvider being called:
> org.eclipse.xtext.common.types.JvmTypeReference, boolean) line: 283"
> So my assumption was that there is a new binding or something other new
> in 2.1 which needs a new guice binding. When I go down the stack I see
> it will get the TypeProvider from this line:
> line: 286
> and I could not find any guice element in "getGenericTypeContext()". The
> TypeProvider comes from the class "JvmFeatureDescription" and I don't
> now where this is coming from.
> So is it a new 2.1 thing? Any ideas on the binding?
Powered by FUDForum
. Page generated in 0.01757 seconds