summaryrefslogtreecommitdiffstats
path: root/bpmn/MSOCommonBPMN/src/main/resources/META-INF
AgeCommit message (Collapse)AuthorFilesLines
2018-07-31Containerization feature of SOBenjamin, Max (mb388a)6-41/+40
Change-Id: I95381232eeefcd247a66a5cec370a8ce1c288e18 Issue-ID: SO-670 Signed-off-by: Benjamin, Max (mb388a) <mb388a@us.att.com>
2018-04-02SO application deployment issuesRob Daugherty1-0/+32
There are a few problems here. 1) Hibernate definitions for a few tables don't match the column definitions in the MySQL schema scripts. 2) The process engine in MSOInfrastructureBPMN is defined incorrectly. 3) Several bpmn flows have errors that block deployment. Change-Id: I029238b82736a3d4977fdf56416c5feb2705b041 Issue-ID: SO-557 Signed-off-by: Rob Daugherty <rd472p@att.com>
2018-03-14AT&T 1712 and 1802 release codeRob Daugherty3-32/+3
This is code from AT&T's 1712 and 1802 releases. Change-Id: Ie1e85851e94bc66c4d9514a0226c221939531a04 Issue-ID: SO-425 Signed-off-by: Rob Daugherty <rd472p@att.com>
2017-11-08Clean up Process Engine selection logicRob Daugherty1-1/+1
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>
2017-10-09MSOCommonBPMN flows are not being deployedRob Daugherty1-0/+32
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>
2017-05-03[MSO-8] Remove files that crash the commonBPMNDeterme, Sebastien (sd378r)1-81/+0
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>
2017-05-02[MSO-8] Second step of the rebase for MSODeterme, Sebastien (sd378r)1-37/+37
Second rebase containing additional features for MSO + total reworking of the BPMN structure + Notification flow can now be added at the end of some BPMN flows Change-Id: I7e937c7a0ba1593ca85e164a093f79c7e38b6ce0 Signed-off-by: Determe, Sebastien (sd378r) <sd378r@intl.att.com>
2017-04-11[MSO-8] Update the maven dependencyxg353y2-0/+118
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>