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) 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
