I just commited an initial impl of a deployment cache, which sits between a DeploymentScanner and MainDeployer.
The actual storage of deployments is handled by a pluggable DeploymentStore component. I added a simple local file version which is probably good enough for most cases. Please before you start bitching about the abstraction, go look at the code and see how the seperation makes both components simpliler (marc =P). Currently a cached deployment url will only become invalid if the orinigal url changes. I imagine that we should add a pluggable policy/period based clean up of undeployed cached urls as well as expose mgmt over the store. I didn't spend too much time testing this for thread safty and whatever, so it could use some more pounding. I updated the default jboss-service.xml to have commeted instructions on how to enable the cache and I will update the NetBoot demo files to use this by default in the days to come... to tired to do it now. Finally, I did run the testsuite and even though the failure/error count is higher than my usual limit... I am thinking that I didn't break anything major. We really need to fix this so it always runs clean unless something is broken. Anyways, please forgive me if I did break something... I can't really tell. Enjoy, --jason _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
