Looks like the ESB deployers can't use a non-absolute path as the key because those are not immediate children of the Axis2 repository directory. In carbon, repository/deployment/server directory is used as the Axis2 repository. But ESB artifacts are under repository/deployment/server/synapse-configs/default/. So those must be registered using absolute paths.
So as I can't properly calculate the key, I'll check whether the deployment directory name is a substring of the key. Thanks, ~Isuru On Wed, May 23, 2012 at 11:49 AM, Isuru Suriarachchi <[email protected]> wrote: > In the new C-App implementation, I want to access the relevant Axis2 > Deployer through the Axis2 deployment engine. For all other types of > artifacts, I can access it just by providing the deployment directory and > the extension as follows. > > deploymentEngine.getDeployer("bpel", "zip"); > > But when I try the same for ESB, it doesn't work because the key provided > at the registration of the Deployers are absolute paths of the deployment > directories. Please see the attachment. So here are my questions. > > 1. Why can't the ESB deployers be registered through the component.xml? Is > there a special reason? > 2. Where is the code which programetically register deployers? > 3. Why are those registered with the absolute paths? > > Thanks, > ~Isuru > > -- > Isuru Suriarachchi > Senior Technical Lead > WSO2 Inc. http://wso2.com > email : [email protected] > blog : http://isurues.wordpress.com/ > > lean . enterprise . middleware > > -- Isuru Suriarachchi Senior 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
