> Also... why are you using autodeployment on a production system? You can > write a little program to deploy the packages you want in the order you > want, the testsuite has lots of examples of this, see esp. the > JBossTestServices class. I think there's a way to do this through a > servlet or jsp also, I think Andreas wrote an ejb adaptor or connector for > the mbean server. >
We used it in production because its fast and easy to maintain. No need to keep/maintain a list of bean dependencies. Remember, I don't want Jetty to startup until everything is done, that's the real problem and I bet many other apps will have the same problem. You shouldn't serve HTTP requests until JBoss is ready. > > Finally: I don't think any logic in AutoDeployer changed. If you put the > mbeans you want to start last at the end of the main > jboss-service file are > they deployed before autodeployer goes through and deploys everything it > can find? If so, this may be an accident of the ordering of deployers and > deploy directories in the autodeployer configuration, and you > might be able Nope, AutoDeployer behavior definately changed. I put an mbean right after the autodeployer declaration in jboss-service.xml and that mbean gets executed at the same time as the autodeployer is deploying things. That mbean does not wait until the AutoDeployer has finished deploying everything. My instincts tell me that you will piss off a lot of people with this behaviour. I've answered many questions on the User list about "How can write initializer classes like Weblogic?" initializer classes meaning classes that get run after the app server has booted. I always tell them, write an MBean. Since MBeans declared after the AutoDeployer will start before the AutoDeployer finishes, I"m betting you'll break a lot of applications.(Mercantec's is definately one of them since they have both an initializer mbean and the dependency of Jetty not starting up until everything is deployed.) > to reorder these to get the results you want. I would be hesitant to rely > on this for a production system. > Doesn't AutoDeploy = HotDeploy. You can't hot deploy unless you autodeploy it? Is this true? Bill _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
