Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 347109

Summary:	Injecting both TypeConformanceComputer and XbaseTypeConformanceComputer
Product:	[Modeling] TMF	Reporter:	Esa Ryhänen <erules>
Component:	Xtext	Assignee:	Project Inbox <tmf.xtext-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	sebastian.zarnekow, sven.efftinge
Version:	2.0.0	Flags:	sebastian.zarnekow: juno+
Target Milestone:	RC2
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Esa Ryhänen

2011-05-25 02:40:03 EDT

Build Identifier:  M20110210-1200

Xbase classes gets TypeConformanceComputer injected in some cases, and in other cases XbaseTypeConformanceComputer gets injected. For example XbaseJavaValidator gets TypeConformanceComputer injected, and FeatureCallChecker gets XbaseTypeConformanceComputer injected.

This requires binding a custom type conformance computer to both XbaseTypeConformanceComputer and TypeConformanceComputer when one binding should be enough.



Reproducible: Always

Comment 1 Sebastian Zarnekow

2012-03-07 11:11:52 EST

We should make sure that we do not stumble accross this one.

Comment 2 Sebastian Zarnekow

2012-04-02 16:39:30 EDT

Fixed another case where we injected the XbaseTypeConformanceComputer. Solution for comment #1 still pending.

Comment 3 Sven Efftinge

2012-05-29 03:41:46 EDT

I checked the current code base. There are no references to XbaseTypeConformanceComputer other than bindings and tests.

Comment 4 Eclipse Webmaster

2017-10-31 11:07:55 EDT

Requested via bug 522520.

-M.

Comment 5 Eclipse Webmaster

2017-10-31 11:19:25 EDT

Requested via bug 522520.

-M.