Right, we've already talked about that. But can Ace handle the simple use case I outlined?
On Thursday, May 7, 2009, Marcel Offermans <[email protected]> wrote: > On May 7, 2009, at 16:05 , Guillaume Nodet wrote: > > > Well, deployment admin has the major drawback of not being able to > share any bundle between deployments. > Hence, your deployed applications are in complete isolation, which > might be good, or bad, depending on your needs. > Take a simple example where you have a shell installed and you want to > deploy a new service along with its commands. The deployment admin > would not really allow to do that afaik. > I may be wrong, but that's my understanding of deployment admin. > > > You are right about the no sharing policy in DeploymentAdmin. That's why Ace > has chosen to put all bundles that should go to a specific target in one > deployment package. There are other reasons why you want that too, for > example because this allows you to always have one transaction when doing an > update. The downside of this approach is that you probably need a system that > dynamically generates these deployment packages, but that's where Ace comes > in. > > Greetings, Marcel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Cheers, Guillaume Nodet ------------------------ Blog: http://gnodet.blogspot.com/ ------------------------ Open Source SOA http://fusesource.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
