Hi all, As per few discussions we did on C-App deployment, we identified that the current C-App deployment process causes problems in cluster with deployment synchronizer. Currently the C-App deployer reads different artifacts and copy those into relevant hot directories in the Axis2 repository (repository/deployment/server/xxx). When these artifacts and the original C-App are synchronized to a different node, there are conflicts.
So as a solution, I've already implemented a way in which the C-App extracts the individual artifacts into a temp directory and directly call the relevant deployer for the artifact. This works well for aar services etc. which won't get changed after first deployment. However, I wonder ESB artifacts will have a different impact on this because the user can edit the ESB configuration through the UI and then it internally get serialized to the original xml file in the repository. But in this new approach, original artifact will be in the temp directory. So will that be a problem from the ESB side? And also please let me know if there are any other possible downsides of this approach which you can think of. Thanks, ~Isuru -- Isuru Suriarachchi Technical Lead WSO2 Inc. http://wso2.com email : [email protected] blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
