In the method canGenerated you have to return true for your project types.

In the method canGenerated you have to return true for your project types.

−

The prefix "GenClass" says this adapter works with the GenClass class of the genmodel.

+

The prefix "GenClass" says this adapter works with the GenClass class of the genmodel, but this is just a naming convention .

In accordance to this you have to configure the extension point or you write a GeneratorAdapterFactory.

In accordance to this you have to configure the extension point or you write a GeneratorAdapterFactory.

Line 40:

Line 40:

Take care not all combinations and of project type and adapter type produce output. (e.g. I had no luck in the combination GenClass and EDITOR project)

Take care not all combinations and of project type and adapter type produce output. (e.g. I had no luck in the combination GenClass and EDITOR project)

+

+

== Package Generator Adapter ==

+

+

If you write a GenPackage generator adapter you should verify in your generate method (in most cases) if it is required to generate an e.g. new class for it.

+

The package in the model may on a higher level, but you get a call for all (selected) packages in the model.

+

+

<source lang="java">

+

+

if (genPackage.hasConcreteClasses()) {

+

message = "Generating class XYZ"; /

+

monitor.subTask(message);

+

+

generateJava(....);

+

} else {

+

monitor.worked(1);

+

}

+

</source>

+

+

A good example is the class GenPackageGeneratorAdapter of EMF itself, you can find it simply by the "Open Type..." command.

+

+

= Dynamic Templates & Generator Adapter =

+

+

To combine a Generator Adapter and a Dynamic Templates you can add the following URI in the GemModel "Template Directory" property

+

* platform:/plugin/<plugin-id>/templates

+

+

If you have some problems during generation (e.g. it generate still the old version) it may help to remove the (hidden) project ".JETEmitter" from you testing workspace (if you just delete it don't forget to refresh the workspace)

GeneratorAdapter Class

The GenBaseGeneratorAdapter base class provide you the basic implementation you have to override:

canGenerate

generateXXXX

It's depend of the project type what generate method's you override. The following types you know from the menu in the Gen Model.

MODEL_PROJECT_TYPE

EDIT_PROJECT_TYPE

EDITOR_PROJECT_TYPE

TESTS_PROJECT_TYPE

In the method canGenerated you have to return true for your project types.

The prefix "GenClass" says this adapter works with the GenClass class of the genmodel, but this is just a naming convention .

In accordance to this you have to configure the extension point or you write a GeneratorAdapterFactory.
All adapters types are:

GenPackage Adapter

GenEnum Adapter

GenModel Adapter

GenClass Adapter

Take care not all combinations and of project type and adapter type produce output. (e.g. I had no luck in the combination GenClass and EDITOR project)

Package Generator Adapter

If you write a GenPackage generator adapter you should verify in your generate method (in most cases) if it is required to generate an e.g. new class for it.
The package in the model may on a higher level, but you get a call for all (selected) packages in the model.

A good example is the class GenPackageGeneratorAdapter of EMF itself, you can find it simply by the "Open Type..." command.

Dynamic Templates & Generator Adapter

To combine a Generator Adapter and a Dynamic Templates you can add the following URI in the GemModel "Template Directory" property

platform:/plugin/<plugin-id>/templates

If you have some problems during generation (e.g. it generate still the old version) it may help to remove the (hidden) project ".JETEmitter" from you testing workspace (if you just delete it don't forget to refresh the workspace)

JET Templates

The included JET Templates or better the static JET template classes have to be generated with the "old/basic" JET implementation.
(choose "Convert Project to JET Project" in new wizard and do not create a "JET Transformation Project")

The M2T JET project even in JET 1 mode produces a not compatible code: see BUG 333811