• Home
• Download
• Documentation
• Support
• Community
• Developers

• Getting Started
• Installation
  • Install Pre-Configured Eclipse With Xtext
  • Install Xtext From Update Site
• 5 Minutes Tutorial
  • Creating A New Xtext Project
  • Generating The Language Infrastructure
  • Try The Editor
  • Conclusion
• 15 Minutes Tutorial
  • Create A New Xtext Project
  • Write Your Own Grammar
  • Generate Language Artifacts
  • Run the Generated IDE Plug-in
  • Second Iteration : Adding Packages and Imports
• 15 Minutes Tutorial - Extended
  • Writing a Code Generator With Xtend
  • Unit Testing the Language
  • Creating Custom Validation Rules
• Five simple steps to your JVM language
  • Step One: Create A New Xtext Project
  • Step Two: Write the Grammar
  • Step Three: Generate Language Artifacts
  • Step Four: Define the Mapping to JVM Concepts
  • Step Five : Try the Editor!
• Reference Documentation
• Overview
  • What is Xtext?
  • How Does It Work?
  • Xtext is Highly Configurable
  • Who Uses Xtext?
  • Who is Behind Xtext?
  • What is a Domain-Specific Language
• The Grammar Language
  • A First Example
  • The Syntax
  • Ecore Model Inference
  • Grammar Mixins
  • Common Terminals
• Configuration
  • The Language Generator
  • Dependency Injection in Xtext with Google Guice
• Runtime Concepts
  • Runtime Setup (ISetup)
  • Setup within Eclipse-Equinox (OSGi)
  • Logging
  • Validation
  • Linking
  • Scoping
  • Value Converter
  • Serialization
  • Formatting (Pretty Printing)
  • Fragment Provider (Referencing Xtext Models From Other EMF Artifacts)
  • Encoding in Xtext
• IDE Concepts
  • Label Provider
  • Content Assist
  • Quick Fixes
  • Template Proposals
  • Outline View
  • Hyperlinking
  • Syntax Coloring
• Xtext and Java
  • Plug-in Setup
  • Referring to Java Elements using JVM Types
  • Referring to Java Types Using Xbase
  • Inferring a JVM Model
  • Using Xbase Expressions
  • Xbase Language Reference
• MWE2
  • Examples
  • Language Reference
  • Syntax Reference
• Xtend
  • Getting Started
  • Classes and Functions
  • Expressions
• Integration with EMF and Other EMF Editors
  • Model, Ecore Model, and Ecore
  • EMF Code Generation
  • XtextResource Implementation
  • Integration with GMF Editors
• Appendix
• Migrating from Xtext 1.0.x to 2.0
  • Take the Shortcut
  • Migrating Step By Step
  • Now go for then new features
• Migrating from Xtext 0.7.x to 1.0
  • Migrating Step By Step

Xtext and Java

The following chapter demonstrates how to integrate your own DSL with Java. We will do this in four stages: First, you will learn how to refer to existing Java elements from within your language. Then you will use Xbase to refer to generic types. In the third step, you will map your own DSL's concepts to Java concepts. Last but not least, you will use both Java types and your concepts within Xbase expressions and execute it.

Throughout this chapter, we will step by step improve the domain model example from the tutorial.

Top

Plug-in Setup

In the following, we are going to use the JVM types model and the Xbase language library. To make these available to your language, you have to add a couple of dependencies. In the runtime plug-in of your language, add dependencies to

• org.eclipse.xtext.common.types
• org.eclipse.xtext.xbase and
• org.eclipse.xtext.xtend2.lib if you are using Xtend to implement components.

Your UI plug-in needs dependencies to

• org.eclipse.xbase.ui
• org.eclipse.xtext.common.types.ui

Additionally, you have to register the genmodel of Xbase to the standalone setup of your MWE2 workflow and make sure the TypesGeneratorFragment (src) and the XbaseGeneratorFragment (src) are included:

To avoid running out of memory when regenerating, you increase the maximum heap size and the permanent generation space in the run configuration of your workflow. We recommend at least

-Xmx512m -XX:MaxPermSize=128m

in the VM Arguments section of the Arguments tab. If you are experiencing ambiguity warnings from Antlr, the usual countermeasures apply.