Christoph Gritschenberger
added a comment - 15/Oct/12 11:54 Alright, we revisited the quickstart-scenario and considered it way to complicated. So we designed a new one.
The idea is now the following:
2 Domains and 1 Engineering Object
One Connector for each domain that just watch some file and throw events when they are updated.
Rules/Workflows make sure that the changes in one domain are propagated to the corresponding artifact in the other domain's connector.
Several transformation descriptions will be required for this:
Tool-model A <-> Domain A
Domain A <-> Eng Object
Eng Object <-> Domain B
Domain B <-> Tool-model B

A FileWatcher-connector was introduced with OPENENGSB-3375.
The next step is an itest that:

Creates two of them using different tool-specific models

Rules that listen to Events introduced by OPENENGSB-3426
--> take the tool-model from the commit, transform it and commit to the domain-model
--> take the domain-model from a commit and distribute it to all other tools (should use the transparent transformation)
In addition to the tool-models transformations for both to the domain-model must be added (both-ways).

Christoph Gritschenberger
added a comment - 12/Dec/12 11:13 A FileWatcher-connector was introduced with OPENENGSB-3375 .
The next step is an itest that:
Creates two of them using different tool-specific models
Rules that listen to Events introduced by OPENENGSB-3426
--> take the tool-model from the commit, transform it and commit to the domain-model
--> take the domain-model from a commit and distribute it to all other tools (should use the transparent transformation)
In addition to the tool-models transformations for both to the domain-model must be added (both-ways).