Age | Commit message (Collapse) | Author | Files | Lines |
|
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>
|
|
Flows in the MSOCommonBPMN jar, which is embedded in the
MSOInfrastructureBPMN war, are not being deployed.
MSOCommonBPMN needs a processes.xml file.
I'm also fixing a problem with CustomE2EGetService.bpmn, which claims
it is the GenericGetService flow. This creates a conflict with the
real GenericGetService flow.
Issue: SO-199
Change-Id: I1ec9d4ad079abf65b5c276b625b46a86805a15e6
Signed-off-by: Rob Daugherty <rd472p@att.com>
|
|
Some files in commonBPMN have been removed as they prevent the war to be
successfully deployed on Jboss + Remove rest interfaces files for
catalog that should not be there anymore
Change-Id: Iaf83f8b60610624e160feac8a96b7eaed7f161d1
Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
|
|
Update the maven depenency for sdc-distribution-client to cooperate with the sdc changes.
Change-Id: I2da936e5c40cb68c7181bb78307192dd5655b5dc
Signed-off-by: xg353y <xg353y@intl.att.com>
|