$subject, due to recent major re-factoring in deployments, the CAR
deployment has been totally broken, did kind of investigation found that...
in synapse Deployer
private Deployer getDeployer(AxisConfiguration axisConfig, String
directory) {
Deployer deployer = null;
// access the deployment engine through axis config
DeploymentEngine deploymentEngine = (DeploymentEngine)
axisConfig.getConfigurator();
String tenantId = AppDeployerUtils.getTenantIdString(axisConfig);
*SynapseEnvironmentService environmentService =
DataHolder.getInstance().*
* getSynapseEnvironmentService(Integer.parseInt(tenantId));*
if (environmentService != null) {
String synapseConfigPath =
ServiceBusUtils.getSynapseConfigAbsPath(
environmentService.getSynapseEnvironment().getServerContextInformation());
String endpointDirPath = synapseConfigPath
+ File.separator + directory;
deployer = deploymentEngine.getDeployer(endpointDirPath,
ServiceBusConstants.ARTIFACT_EXTENSION);
}
return deployer;
}
the above highlighted section..(basically SynapseAppDeployer) getting
invoked before TenantServiceBusInitializer component initialized, thus it
can not find relevant synapse env... any thoughts how we should mitigate
this problem ?
anyway have we EVER done any sort of testings with those deployment
changers with ESB specially in the *context of Multitenancy mode ? *sounds
like never..
Cheers,
Dushan Abeyruwan
Associate Tech Lead
*Integration Technologies Team*
*WSO2 Inc. http://wso2.com/ <http://wso2.com/>*
*Mobile:(+94)714408632 <%28%2B94%29714408632>*
_______________________________________________
Dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/dev
