[DEECo] [d3scomp/JDEECo] ee72bc: The split of coordinator vs. member scheduling of ...

[GitHub]

  Branch: refs/heads/newgen-bures
  Home:   https://github.com/d3scomp/JDEECo
  Commit: ee72bc0db1e47c805a8397262b187582ed5d0446
      https://github.com/d3scomp/JDEECo/commit/ee72bc0db1e47c805a8397262b187582ed5d0446
  Author: Tomas Bures <bures at d3s.mff.cuni.cz>
  Date:   2013-11-03 (Sun, 03 Nov 2013)

  Changed paths:
    M jdeeco-core/model/RuntimeModel.ecore
    M jdeeco-core/model/RuntimeModel.ecorediag
    M jdeeco-core/src/cz/cuni/mff/d3s/deeco/knowledge/KnowledgeManagersView.java
    M jdeeco-core/src/cz/cuni/mff/d3s/deeco/model/runtime/api/EnsembleDefinition.java
    M jdeeco-core/src/cz/cuni/mff/d3s/deeco/model/runtime/impl/EnsembleDefinitionImpl.java
    M jdeeco-core/src/cz/cuni/mff/d3s/deeco/model/runtime/impl/RuntimeMetadataPackageImpl.java
    M jdeeco-core/src/cz/cuni/mff/d3s/deeco/model/runtime/meta/RuntimeMetadataPackage.java
    R jdeeco-core/src/cz/cuni/mff/d3s/deeco/task/EnsembleCoordinatorTask.java
    R jdeeco-core/src/cz/cuni/mff/d3s/deeco/task/EnsembleMemberTask.java
    A jdeeco-core/src/cz/cuni/mff/d3s/deeco/task/EnsembleTask.java
    M jdeeco-core/src/cz/cuni/mff/d3s/deeco/task/Task.java
    M jdeeco-core/test/cz/cuni/mff/d3s/deeco/model/runtime/SampleRuntimeModel.java
    M jdeeco-core/test/cz/cuni/mff/d3s/deeco/task/EnsembleTaskTest.java
    M jdeeco-core/test/cz/cuni/mff/d3s/deeco/task/ProcessTaskTest.java

  Log Message:
  -----------
  The split of coordinator vs. member scheduling of an ensemble reverted.
It didn't really solve the problem I had in mind (i.e. that knowledge
paths of triggers have to be striped of member/coord prefix) and by
itself, it was an overkill.

There are some more architectural suggestions in the comments.
Essentially it seems that it would make a lot of sense to have separate
trigger listeners:
KnowledgeManager: triggered(Trigger)
KnowledgeManagersView: triggered(ReadOnlyKnowledgeManager, Trigger)
Task: triggered(Task)