So for #3, are we going to support mgt console level changes for artifacts that comes from CApp's ? What are the user requirements and do we actually need this? I thought we decided to remove the editing functionality for artifacts that comes from CApps in mgt console level.
On Mon, Apr 27, 2015 at 7:15 PM, Priyadarssini Kishokumar < [email protected]> wrote: > Hi All, > > I'm implementing $Subject with related redmine[1] > > The main tasks should be > 1. Identifying the artifacts deployed with CAR > 2. Changes done through the management console for CAR artifacts should > not be saved in default deployment location > 3. Persisting the changes into the CAR file. > > Currently I'm identifying the artifacts coming from CAR and set the > details in the synapse level. By this way requirements 1 & 2 can be solved. > To persisting into CAR file, we need to get the CAPP name in the synapse > level. Currently I'm doing by modify the "DeploymentFileData" in the axis2. > In carbon application deployment "SynapseAppDeployer" class passing the > DeploymentFileData to synapse. This is the only place the deployed file > details are passing to synapse. To avoid axis2 level changes, we need to > come up with a way to send the CAPP file details to synapse. Please advise > a better way to handle this. > > > [1] https://redmine.wso2.com/issues/3837 > > -- > Priya Kishok > Software Engineer > WSO2, Inc : http://wso2.com > Mob : +94774457404 > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Kishanthan Thangarajah* Associate Technical Lead, Platform Technologies Team, WSO2, Inc. lean.enterprise.middleware Mobile - +94773426635 Blog - *http://kishanthan.wordpress.com <http://kishanthan.wordpress.com>* Twitter - *http://twitter.com/kishanthan <http://twitter.com/kishanthan>*
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
