Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 363290 - Custom TypeProvider is not used in some circumstances
Summary: Custom TypeProvider is not used in some circumstances
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: unspecified   Edit
Hardware: Macintosh Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-11-09 06:43 EST by Kai Kreuzer CLA
Modified: 2017-10-31 11:19 EDT (History)
2 users (show)

See Also:
sebastian.zarnekow: kepler+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kai Kreuzer CLA 2011-11-09 06:43:32 EST
Build Identifier: Xtext 2.1.0

Usecase as follows:
- A custom ITypeProvider is implemented which extends XbaseTypeProvider
- This type provider is bound to Class<? extends ITypeProvider> in the RuntimeModule.

This leads to "Type computation is not implemented for..." exceptions, although the type provider implements the type() methods for the relevant types.

As a workaround the custom type provider can be additionally bound to ITypeArgumentContextHelper, which solves the problem.

Please find details on this at http://www.eclipse.org/forums/index.php/t/261225/


Reproducible: Always
Comment 1 Sebastian Zarnekow CLA 2013-04-19 05:43:45 EDT
This became obsolete or fixed in the meantime.
Comment 2 Eclipse Webmaster CLA 2017-10-31 11:08:00 EDT
Requested via bug 522520.

-M.
Comment 3 Eclipse Webmaster CLA 2017-10-31 11:19:32 EDT
Requested via bug 522520.

-M.