On 8/9/06, Peter Klotz <[EMAIL PROTECTED]> wrote:
Hi,
I tried to re-deploy a service-assembly with the SM ant tasks (CLI or from
within SU). It seems what works when copying a SA to the deploy directory,
that
is the SA is re-deployed, does not work with the ant tasks?
[jbi:deploy-service-assembly] <loc-message>Service unit midas-behttp is
already
deployed on component servicemix-http</loc-message>
There seems to be no force flag on the ant task unfortunately.
I'm using the ant tasks because I need to have synchronous deployment with
an ME
right after the deployment. With copying a SA zip to deploy this does not
work,
because the SA is deployed asynchrounously from a other SM thread.
I could of course undeploy first and re-deploy, is this required?
Yes, this is required by the JBI spec.
Is there a programatic way to deploy a SA in SM from within a class that
extends
ComponentSupport? If so how?
You could use:
JBIContainer container = ((ComponentContextImpl)
getContext()).getContainer();
container.updateExternalArchive("url or path to archive");
The archive can be a JBI component, SL or SA.
Peter
--
Cheers,
Guillaume Nodet
