+1 It need to be pass through the application definition and we can pass that value through event or cartridge payload to the cartridge.IMO If we can pass it through the cartridge payload , we will able to maintain that value as system parameter and can use where ever we want.
Thanks, Gayan On Sun, Feb 15, 2015 at 10:47 PM, Imesh Gunaratne <[email protected]> wrote: > Hi Chamila, > > A good finding! Yes I also cannot see the autoCommit attribute in Artifact > Repository bean in the application definition. > > This functionality might be needed for certain cartridges for propagating > changes that they do via the UI. Therefore we may need to add it. > > Thanks > > On Sun, Feb 15, 2015 at 5:21 PM, Chamila De Alwis <[email protected]> > wrote: > >> Hi, >> >> In the cartridge agent's artifact management, the auto commit flag can be >> set either by configuration (ex: Puppet) or via the ArtifactUpdatedEvent. >> Currently this is read from the configuration only. >> >> Is this now specified as a subscribable info in the application >> definition? I can't find a sample with this value specified. >> >> If that is the case, then it should be read from the event itself, rater >> than the configuration, since at configuration time it is not possible to >> specify that value correctly. >> >> It is the same with auto checkout functionality. >> >> WDYT? >> >> Python agent configuration - agent.conf >> >> Java agent configuration - stratos.sh(.erb) >> >> >> >> Regards, >> Chamila de Alwis >> Software Engineer | WSO2 | +94772207163 >> Blog: code.chamiladealwis.com >> >> >> > > > -- > Imesh Gunaratne > > Technical Lead, WSO2 > Committer & PMC Member, Apache Stratos > -- Gayan Gunarathne Technical Lead WSO2 Inc. (http://wso2.com) email : [email protected] | mobile : +94 766819985
