Why don't you call the second form of the deployment method?
public List deploy(boolean inPlace,
File planFile,
File moduleFile,
File targetFile,
boolean install,
String mainClass,
String classPath,
String endorsedDirs,
String extensionDirs,
String targetConfigurationStore) throws
DeploymentException {
-dain
On May 2, 2006, at 5:24 AM, Sachin Patel wrote:
After debugging this morning why I can't deploy to a different
configuration store, the source of the problem is the following...
In o.a.g.deployment.Deployer, in the call to
deploy(inPlace, planFile, moduleFile, null, true, null, null, null,
null, null);
The last param is the configuration store, which is being passed in
null, thus resolves later to...
if (targetConfigurationStore != null) {
AbstractName targetStoreName = new AbstractName(new URI
(targetConfigurationStore));
store = (ConfigurationStore) kernel.getGBean(targetStoreName);
} else {
store = (ConfigurationStore) stores.iterator().next();
}
The else statement picks up the "Local" configuration store, thus
no matter what Target's you pass in, "Local" is always used.
Aaron, I'm not sure if this is the problem you were referring to
when you stated that "targets are being ignored"? Or wether you
were referring to the DistributeCommand using only the first index
of the passed targets, the rest being ignored.
- sachin
