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

Bug 354596

Summary: Add XtypeQualifiedNameProvider
Product: [Modeling] TMF Reporter: Karsten Thoms <karsten.thoms>
Component: XtextAssignee: Project Inbox <tmf.xtext-inbox>
Status: CLOSED DUPLICATE QA Contact:
Severity: enhancement    
Priority: P3 CC: sebastian.zarnekow
Version: 2.0.0   
Target Milestone: ---   
Hardware: PC   
OS: Mac OS X - Carbon (unsup.)   
Whiteboard:

Description Karsten Thoms CLA 2011-08-12 05:15:57 EDT
The Domainmodel example introduces a specialized IQualifiedNameProvider:

==============================================================================
public class DomainmodelQualifiedNameProvider extends DefaultDeclarativeQualifiedNameProvider {

	@Inject
	private IQualifiedNameConverter converter;
	
	QualifiedName qualifiedName(JvmGenericType type) {
		return converter.toQualifiedName(type.getQualifiedName());
	}
}
==============================================================================

However, this kind of customization is required always when using Jvm types. Forgetting to customize this is a common point of failure. Thus it would be better when this class is added to Xtype (as class XtypeQualifiedNameProvider) and automatically bound to the runtime module of a language if this derives from Xtype.
Comment 1 Sebastian Zarnekow CLA 2011-08-12 05:18:33 EDT

*** This bug has been marked as a duplicate of bug 350812 ***