Difference between revisions of "AutowireHelper"
| Line 1: | Line 1: | ||
| − | The purpose of an AutowireHelper is the model to model transformation of a entity model or a DTO model to an ecview model. An ecview model represents the model for a dialog. It either can be generated by an AutowireHelper or manually by using the ui model. This enables the system to create user interfaces automatically according to the underlying entity. As entity model changes, dialogs using the autobinding keyword and referencing the associated DTO do the same. An autowiring implements rules how to interprete data types and structural information to a valid ecview model. AutowireHelper uses metadata associated with the entity model to modify the transformation behaviour. | + | The purpose of an AutowireHelper is the model to model transformation of a entity model or a DTO model to an ecview model. An ecview model represents the model for a dialog. It either can be generated by an AutowireHelper or manually by using the ui model. This enables the system to create user interfaces automatically according to the underlying entity. As entity model changes, dialogs using the autobinding keyword and referencing the associated DTO do the same. An autowiring implements rules how to interprete data types and structural information to a valid ecview model. AutowireHelper uses metadata associated with the entity model to modify the transformation behaviour. The generated ecview model is persisted as xmi file and will be interpreted during runtime by a renderer consuming the model. The resulting dialog follows the E4 annotation style and embeds as a view to be placed in an E4 MPart. The placment is done by using Perspective DSL. |
To include a custom autowire helper as delegate for the Service to use an entry in the plugin.xml is required. | To include a custom autowire helper as delegate for the Service to use an entry in the plugin.xml is required. | ||
Revision as of 06:49, 19 October 2017
The purpose of an AutowireHelper is the model to model transformation of a entity model or a DTO model to an ecview model. An ecview model represents the model for a dialog. It either can be generated by an AutowireHelper or manually by using the ui model. This enables the system to create user interfaces automatically according to the underlying entity. As entity model changes, dialogs using the autobinding keyword and referencing the associated DTO do the same. An autowiring implements rules how to interprete data types and structural information to a valid ecview model. AutowireHelper uses metadata associated with the entity model to modify the transformation behaviour. The generated ecview model is persisted as xmi file and will be interpreted during runtime by a renderer consuming the model. The resulting dialog follows the E4 annotation style and embeds as a view to be placed in an E4 MPart. The placment is done by using Perspective DSL.
To include a custom autowire helper as delegate for the Service to use an entry in the plugin.xml is required. See the following code as template:
<?xml version="1.0" encoding="UTF-8"?>
<?eclipse version="3.4"?>
<plugin>
<extension
point="org.lunifera.ecview.dsl.autowireDelegate">
<autowireDelegate
autowireDelegateClass="de.compex.autowirehelper.AutowireHelper"
id="de.compex.autowireHelper.autowireDelegate">
</autowireDelegate>
</extension>
</plugin>
