Global scoping
Xtext has a default mechanism for global scoping that allows you to refer to elements defined in a different file, possibly in a different project of the workspace; in particular, it uses the dependencies of the Eclipse projects. For Java projects, it uses the classpath of the projects. Of course, this mechanism relies on the global index.
Note
Global scoping is implied by the fact that the default scoping mechanism always relies on an outer scope that consists of the visible object descriptions in the index.
With the default configuration in the MWE2, this mechanism for global scoping works out of the box. You can experiment with a project with some Entities DSL files. You can see, as illustrated in the following screenshot, that ...
Get Implementing Domain-Specific Languages with Xtext and Xtend now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
