On Friday 14 November 2003 15:06, davout wrote: > I read somewhere that either Merlin or Fortress has... > * Support for distributed deployment; and > * Will work with JBoss > > Is either statement true?
Merlin is moving towards distributed deployment, but Fortress is not. Merlin right now is in a stage where the executable can be given a remote deployment descriptor and it will pick up the components and assemble the application. However, it is not dynamic, i.e. if the deployment descriptor changes, it will re-deploy. We are still discussing the best road to get there. I don't think anyone favour the "drop everything and start over" as J2EE containers think is Ok. Instead, I think people are inclined to favour a "Service Discovery" contract, where services may come and go independently. That would mean that the container can announce "Service No Longer Available" without the user code choking, and "later" announce "Service Now Available", to handle upgraded code, and many other things (Moving Agents, Self-balancing). JBOSS is a big chapter. I think it is rather simple to drop in Fortress as a container inside JBoss. I don't know if you can do that with Merlin, but I think so. Can you run JBoss as a component inside Merlin?? I don't think so at the moment. Will we be able to do it? Maybe, maybe not... Is it desirable? I don't know that either (I don't like J2EE :o) ) Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
