Alexey Loubyansky [http://community.jboss.org/people/alex.loubyansky%40jboss.com] created the discussion "using BatchBuilder for deploying services on startup" To view the discussion, visit: http://community.jboss.org/message/557918#557918 -------------------------------------------------------------- This is what we currently do, i.e. deployments listed in standalone/domain xml are added to BatchBuilder. BatchBuilder is supposed to treat services added to the batch as one deployment, i.e., as I understand, deploy all of them or none if at least one of the services failed. We touched upon a question (in another thread) whether the server should fail to start if one of its deployments failed. It was decided that the error should be logged but the server continue deploying other services. In this case, we shouldn't use BatchBuilder during server start-up the way we do now. Or perhaps the concept of BatchBuilder should be advanced and a few different implementations should be provided, e.g. - if any of the deployments fail then fail the whole batch; - if some specific of the deployments fail then fail the whole batch; - each deployment isolated and has no affect on others (kind of a fake batch or no batch). -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/557918#557918] Start a new discussion in JBoss AS7 Development at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]