Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 317977 - No implicit import of elements in different resources within the same namespace
Summary: No implicit import of elements in different resources within the same namespace
Status: CLOSED FIXED
Alias: None
Product: TMF
Classification: Modeling
Component: Xtext (show other bugs)
Version: 1.0.0   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: M4   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-06-25 09:33 EDT by Sebastian Benz CLA
Modified: 2017-09-19 17:58 EDT (History)
2 users (show)

See Also:
sebastian.zarnekow: indigo+

Attachments
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 Sebastian Benz CLA 2010-06-25 09:33:24 EDT 
Given two files A and B with the same namespace "test". By default elements in resource A cannot implicitly reference elements in B even though they have the same namespace. However, when importing the namespace "test" from a third file C, elements from A and B can be referenced. A workaround is to create by default an ImportNormalizer for the namespace of the context in ImportedNamespaceAwareLocalScopeProvider#internalGetImportNormalizers(EObject context).
Comment 1 Sebastian Zarnekow CLA 2010-12-13 17:15:39 EST 
This one may be fixed with the new impl of the imported namespace handling.
Comment 2 Sven Efftinge CLA 2010-12-14 02:47:46 EST 
Yes, it is.
Comment 3 Karsten Thoms CLA 2017-09-19 17:46:58 EDT 
Closing all bugs that were set to RESOLVED before Neon.0
Comment 4 Karsten Thoms CLA 2017-09-19 17:58:03 EDT 
Closing all bugs that were set to RESOLVED before Neon.0