Hi folks, I just put the latest version of J2eeDeployer into cvs. I hope he gives now anyhow more self explaining error messages in case of failure. Furthermore I ve changed the way he keeps track of the current deployments. There is no central file anymore. The deployments are downloaded to a directory with the applications name (as usual) and the serialized Deployment meta info is now placed into this directory (its somehow more consistent if somebody modifies the deployment directory, which is not recommended). I also changed his behaviour on start/stop. Currently he does nothing on startup and on stop he undeployes (and removes all files) as it was before. This I needed, because I want to enable the AutoDeployer to use this J2eeDeployer instad of directly using the ContainerFactory as he currently does. Right now I m adding the ability of handling directories as the ContainerFactory does. My goal is to make the autodeploy stuff working as it currently is, but: 1. ejb.jar, web.war and/or application.ear files can be droped to the deploy dir and get deployed 2. unpacked ejb.jars can be droped into the deploy dir (for development, as it is currently possible) 3. redeployment behaves correctly (the autodeployer currently seems to not correctly deploy after a few iterations (right class versions)) I dont see the need for the support of handling unpacked .war and .ear files, because: 1. if you deploy .wars only why are you using jBoss 2. if you wanna deploy .ears in development, its easier to create a target in ant/make/... that creates the package and overwrites the previous one every time you need to redeploy Beside the autodeploy ability with the J2eeDeployer it is furthermore possible to deploy apps (packages only - no directories) through the network by just giving a http url (this works already well). Please give any comments! Open my eyes if I ve missed something! Of course I would welcome if sombody says: hey, cool, may I help you... On my installation (fresh cvs checkout) it works fine, and I can only break it, when I use somehow "corrupted" packages (wrong packaged, files missing, errors in ejb-jar.xml, etc.). So please have a look at the ejb spec and/or others to make sure your packages are well formed. BTW the description of how to package .ear files is in the J2EE spec! \Daniel -- -------------------------------------------------------------- To subscribe: [EMAIL PROTECTED] To unsubscribe: [EMAIL PROTECTED] Problems?: [EMAIL PROTECTED]
