Hi Nandika, Since implementing CApp version support require platform level improvements. We'll try to address this on a future release and I created a public JIRA for that.
[1] https://wso2.org/jira/browse/CARBON-15268 Regards, Manoj *Manoj Kumara |* Senior Software Engineer Inc. *| **lean. enterprise. middleware.* #20, Palm Grove, Colombo 03, Sri Lanka *Mobile:* +94 713 448188 *|** Work:* +94 112 145345 On Fri, Jun 5, 2015 at 11:04 AM, Manoj Kumara <ma...@wso2.com> wrote: > Hi, > > We can check whether CApp is already deployed by getting the CApp list of > a given tenant (please check ApplicationManager class).We check this during > the deployment process as well. > > Will that be helpful during your requirement so you can figure out which > operation is during deployment. > > Regards, > Manoj > > > *Manoj Kumara |* Senior Software Engineer > Inc. *| **lean. enterprise. middleware.* > #20, Palm Grove, Colombo 03, Sri Lanka > *Mobile:* +94 713 448188 *|** Work:* +94 112 145345 > > > On Fri, Jun 5, 2015 at 12:05 AM, Nandika Jayawardana <nand...@wso2.com> > wrote: > >> Hi Manoj, >> >> As Hasitha said, versioning is essential to processes as processes are >> supposed to be long running. Hence we cannot afford to un deploy the older >> version, when a new version is deployed. We need an enhancement in the >> AppDeploymentHandler interface to tell the deployer whether this is a new >> CAR deployment or a update of an existing car deployment. Then in the case >> of update, we can handle the logic such that versioning is preserved. >> >> Regards >> Nandika >> >> On Thu, Jun 4, 2015 at 11:57 PM, Hasitha Aravinda <hasi...@wso2.com> >> wrote: >> >>> Hi Manoj and Hasitha, >>> >>> To preserve older versions of a BPEL artifact, BPS requires to replace >>> exact same BPEL artifacts with an updated one. Currently when an updated >>> Capp is uploaded, it will undeploy old BPEL process and deploy new one. >>> This will cause to remove old BPEL versions. >>> >>> To avoid this, as himasha suggest, we required to know reason for Capp >>> underemployment, ( Capp updated, or removed from management console etc) so >>> that we can handle this on Capp BPEL undeploy logic. I think, this will >>> apply for HumanTask, BPMN versioning as well. >>> >>> Since Capp deployer doesn't support this, we need to see another way to >>> solve this problem. Otherwise Capp will not support BPS versioning feature. >>> >>> >>> Thanks, >>> Hasitha. >>> >>> >>> Hasitha Aravinda, >>> Senior Software Engineer, >>> WSO2 Inc. >>> Email: hasi...@wso2.com >>> Mobile : +1 201 887 1971, +94 718 210 200 >>> >>> On Thu, Jun 4, 2015 at 12:38 PM, Hasitha Hiranya <hasit...@wso2.com> >>> wrote: >>> >>>> Hi, >>>> >>>> This is one of the solutions people are using. >>>> >>>> Name the CAR file as xxx-car-v-1.0 >>>> Name all the artifacts inside it as artifact-xxx-v-1.0 >>>> >>>> Then deploy CAR files. Old ones will not be replaced. The references in >>>> each artifact to one another should be updated. >>>> We can do this to endpoints. >>>> But doing this to all will be cumbersome. >>>> >>>> Thanks >>>> >>>> On Thu, Jun 4, 2015 at 8:11 AM, Manoj Kumara <ma...@wso2.com> wrote: >>>> >>>>> Hi Himasha, >>>>> Please see my inline comments, >>>>> >>>>>> >>>>>> The scenario that we come across is as below. >>>>>> >>>>>> 1. Deploy a C-App containing BPEL artifacts >>>>>> 2. Invoke an instance (instance 1) >>>>>> 3. Redeploy the C-App with updated BPEL artifacts. >>>>>> 4.When redeploying the previous C-App is undeployed which removes >>>>>> the invoked instance (instance 1) as well. >>>>>> >>>>> >>>>> This is the expected behavior. Since CApp get redeployed previously >>>>> deployed artifacts also get un-deployed. >>>>> >>>>>> >>>>>> For our BPEL C-App deployer we have implemented AppDeploymentHandler. >>>>>> We are unable to identify whether the undeployment is a direct >>>>>> undeployment >>>>>> ( user undeploying the C-App from console) or if it is getting undeployed >>>>>> due to a new upload of the same C-App. We are unable to handle the >>>>>> version >>>>>> change since AppDeploymentHandler only provides deployArtifacts >>>>>> and undeployArtifacts methods. >>>>>> >>>>> >>>>> At the moment we don't have CApp version support. When an updated >>>>> CApp get uploaded previous one get undeployed and new one will be >>>>> deployed. >>>>> >>>>> Regards, >>>>> Manoj >>>>> >>>>> _______________________________________________ >>>>> Dev mailing list >>>>> Dev@wso2.org >>>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>>> >>>>> >>>> >>>> >>>> -- >>>> *Hasitha Abeykoon* >>>> Senior Software Engineer; WSO2, Inc.; http://wso2.com >>>> *cell:* *+94 719363063* >>>> *blog: **abeykoon.blogspot.com* <http://abeykoon.blogspot.com> >>>> >>>> >>>> _______________________________________________ >>>> Dev mailing list >>>> Dev@wso2.org >>>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>>> >>>> >>> >>> _______________________________________________ >>> Dev mailing list >>> Dev@wso2.org >>> http://wso2.org/cgi-bin/mailman/listinfo/dev >>> >>> >> >> >> -- >> Nandika Jayawardana >> WSO2 Inc ; http://wso2.com >> lean.enterprise.middleware >> > >
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
