Hi Harshana/Vijitha, > > Before going in to handling C-App versions, we need to have the Artifact > level versioning support. Without Artifact versioning, C-App versioning > does not bring any value to the platform. >
+1 , It would be great to have artifact level versioning support for all artifacts. > AFAIK, we have plans to address this in the up coming product releases. > > However once it is done, C-App versioning needs to be supported. > C-app versioning support is already there with 4.2.0 release. But for utilized this feature in a product, That product should have artifact versioning support as you have mentioned above. Thanks, Shameera. > Thanks and Regards, > Harshana > > > On Mon, Nov 25, 2013 at 10:41 AM, Vijitha Kumara <[email protected]> wrote: > >> >> >> >> On Tue, Nov 19, 2013 at 4:44 PM, Harshana Martin <[email protected]>wrote: >> >>> Hi All, >>> >>> Following are the notes from the meeting on CAR files and C-App Projects. >>> >>> Major Problems and Action Plan: >>> >>> 1. Deployment Order of Artifacts inside a given CAR >>> >>> Solution: >>> >>> - DevS team will own it and will manage the generation of Artifact.xml >>> metadata file with correct order inside the artifact.xml file. >>> - Will fix the DevS exporter as well as Maven Plugins >>> >>> 2. Class Mediator Deployment (In tenants and how to handle hot-update) >>> >> >> >> I think we should also consider versioning support for C-Apps along the >> lines as to avoid any conflicts when that gets implemented (as part of the >> C5 effort). >> >> >> >> Regards, >> Vijitha. >> >> >>> >>> Solution: >>> >>> - Kernel team to own this. >>> - Will follow the same solution used in ESB (URLClassLoader based >>> solution) in kernel when deploying the Class mediators from CAR files. >>> - Will not support hot-update for Custom mediators and will continue to >>> load via dropins folder >>> - If some one need to use Carbon APIs, they have to use Carbon Context >>> APIs instead of OSGi services. >>> >>> 3. DevS unsupported features in ESB 4.8.0 >>> >>> - Kernel team to own this. >>> - We are going to revisit the implementation of Synchronize CAR >>> deployment functionality >>> - With that we are going to provide a mechanism to use Mgt Console for >>> setting security and some other QoS parameters until DevS has the complete >>> support for Security, etc >>> >>> Please feel free to add anything If I've missed. >>> >>> Thanks and Regards, >>> Harshana >>> -- >>> >>> Harshana Martin >>> Associate Technical Lead >>> WSO2 Inc. : http://wso2.com >>> >>> Mobile: +94 775 998 115 >>> Profile: https://www.google.com/profiles/harshana05 >>> Blog: http://harshana05.blogspot.com >>> Twitter: http://twitter.com/harshana05 >>> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Vijitha Kumara >> Senior Software Engineer; WSO2, Inc.; http://wso2.com/ >> email: [email protected] >> >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > > Harshana Martin > Associate Technical Lead > WSO2 Inc. : http://wso2.com > > Mobile: +94 775 998 115 > Profile: https://www.google.com/profiles/harshana05 > Blog: http://harshana05.blogspot.com > Twitter: http://twitter.com/harshana05 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *Software Engineer - WSO2 Inc.* *email: shameera AT wso2.com <[email protected]> , shameera AT apache.org <[email protected]>* *phone: +9471 922 1454* *Linked in : *http://lk.linkedin.com/pub/shameera-rathnayaka/1a/661/561 *Twitter : *https://twitter.com/Shameera_R
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
