"kaobe" wrote : I have not tried it, but it could work for you if you add a depends tag to your deploymentscanner mbean in jboss-service.xml. There you tell it it depends on the FarmMember mbean in farm-service.xml. So it should deploy the farm directory first. | | Another possibility could be to put the mbean definition from farm-service before the one in jboss-service. I think the xml-files are deployed from top to bottom.
Hi Peter, thanks for your remarks. I tried the first one, but it kind of screws up the whole deployment process, so that nothing get's deployed correctly anymore. The second one seemed to be more promising. Until I realized that I need the datasource installed before anything else. So the correct deployment order (for me) would be deploy(datasource)-farm-deploy(rest). I played around a bit and found that I can create a directory deploy.last2 which get's deployed after deploy.last, where the farm-service.xml resides. This does the trick. Now first the datasource and all the other essential stuff from deploy gets installed, then what's in farm, and then the remaining parts of my application. Btw, I'm using JBoss 3.2.4RC2. Greetings Martin View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3836208#3836208 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3836208 ------------------------------------------------------- This SF.Net email is sponsored by: Oracle 10g Get certified on the hottest thing ever to hit the market... Oracle 10g. Take an Oracle 10g class now, and we'll give you the exam FREE. http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user