Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 362287 - DefaultDeclarativeQualifiedNameProvider should contain dispatch method
Summary: DefaultDeclarativeQualifiedNameProvider should contain dispatch method
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 2.1.0   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 enhancement (vote)
Target Milestone: M6   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-10-28 05:55 EDT by Benjamin Schwertfeger CLA
Modified: 2017-10-31 10:59 EDT (History)
2 users (show)

See Also:
jan: juno+

Attachments
Changes for QualifiedNameProvider (1.24 KB, patch)
2011-10-28 05:55 EDT, Benjamin Schwertfeger CLA 		sven.efftinge: iplog+
Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Benjamin Schwertfeger CLA 2011-10-28 05:55:45 EDT 
Created attachment 206120 [details]
Changes for QualifiedNameProvider

The JavaDoc of DefaultDeclarativeQualifiedNameProvider contains the wrong signature of qualifiedName methods to write for dispatcher. The return type has changed with Xtext 2.0 from String to QualifiedName.

The DefaultOutlineTreeProvider contains a method for Object without content to override the method and change the signature easily. This could be adapted also for the NameProvider to make writing the method easier.
Comment 1 Jan Koehnlein CLA 2012-02-24 10:30:10 EST 
Looks good, thanks, but the method qualifiedName should at least be protected. I changed that and pushed it to MASTER.
Comment 2 Eclipse Webmaster CLA 2017-10-31 10:48:39 EDT 
Requested via bug 522520.

-M.
Comment 3 Eclipse Webmaster CLA 2017-10-31 10:59:41 EDT 
Requested via bug 522520.

-M.