Java Reference
In-Depth Information
CHAPTER 8
DSL Packaging and
Deployment
So far, we've developed a series of abstract syntax models, diagrams, and model transfor-
mations. After creating a collection of domain-specific language (DSL)-related artifacts, a
Toolsmith needs to test and deploy them to a Practitioner's workbench. In this chapter, we
explore polishing items, packaging, and deployment options for these artifacts.
Although this topic does not cover the topic, it should become obvious that much of the
code you create to deploy DSLs could be generated from yet another DSL defined to
model the aspects of deployment (not to mention building and packaging aspects).
Feature definition, user interface plug-in, transformation invocation actions, and so on are
all potential targets for a set of code-generation templates and corresponding models.
When it comes to product lines, the information captured to select variation points and
options for generating a set of plug-ins that represent a product are ideally captured in
models and leveraged in this manner.
Before deployment, you must tie up all loose ends. Up to this point, we've been
developing our collection of requirements DSLs in a development workspace and
testing in a runtime instance with all plug-ins. Let's look at a number of check-
list items to make sure our DSLs are generated consistently, in preparation for
feature and product definition.
303
Search WWH ::
Custom Search