summaryrefslogtreecommitdiffstats
path: root/docs/submodules
diff options
context:
space:
mode:
authorRob Daugherty <rd472p@att.com>2017-11-08 18:35:49 -0500
committerGerrit Code Review <gerrit@onap.org>2017-11-09 06:35:47 +0000
commit902558faa7f1923261025ec696086021ce6efb0a (patch)
tree23b6f2936bc3a922d972ea509a191385c9092684 /docs/submodules
parenta9642b82a75ac04ce661f4d5df50896841478565 (diff)
Updated git submodules
Project: so master d750eabf5de2423f0a7c89ffbfbcc0d65bb4623e Clean up Process Engine selection logic Several failed attempts to split the BPMN application into multiple applications with separate camunda process engines have left a mess of confusing classes and process engine definitions. In the Amsterdam release, there should be only one BPMN application war. This is MSOInfrastructureBPMN. MSOCommonBPMN should not be deployed as a separate application. Its classes are compiled into a jar and this is included inside MSOInfrastructureBPMN. The MSOInfrastructureBPMN application should use the "default" process engine. WorkflowAsyncInfrastructureResource and MSOCommonApplication classes are not needed. Issue: SO-322 Change-Id: Ifdb3b33541346b561a16361d1aa791e8342a34fa Signed-off-by: Rob Daugherty <rd472p@att.com>
Diffstat (limited to 'docs/submodules')
m---------docs/submodules/so.git0
1 files changed, 0 insertions, 0 deletions
diff --git a/docs/submodules/so.git b/docs/submodules/so.git
-Subproject 3935e84e0306183450fc080a09fcc1d13ced345
+Subproject d750eabf5de2423f0a7c89ffbfbcc0d65bb4623