Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 354596 - Add XtypeQualifiedNameProvider
Summary: Add XtypeQualifiedNameProvider
Status: CLOSED DUPLICATE of bug 350812
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.0.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-08-12 05:15 EDT by Karsten Thoms CLA
Modified: 2011-08-12 05:18 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
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 ***