How CarbonApp Get Deployed

CApp is a single file which is a combination of artifacts (axis2, data service, proxy service, gadjet server). When deploying a capp in to server it will first copy these artifacts to corresponding directory in CARBON_HOME/repository/deployment/server

ex : /webapp
       /jaxwebapp
       /data service
       /axis2services

On these directories a listener will periodically check for new artifacts and when found it will deploy the relevant artifact of the server. One drawback on the current system is that it's hard to check weather the artifact is actually deployed or not. So we have slightly modified this deployment approach as follows.

According to our new approach when CApp gets deployed these CApp artifacts extracted it to temp location and then CApp deployer calls the relevant deployers of artifacts to deploy. With this approch we can easily check about the artifacts.