David Jencks wrote:
Well, directory scanning hot deployment is a really bad idea and suffers
from innumerable problems of this sort and basically cannot be made to
work. I think we should implement something compatible with other
implementations of this bad idea and tell people not to use it. This
means not altering stuff in the hot deploy directory ourselves but
attempting to monitor it. The other major problem is that it is
completely incompatible with j2ee 1.4/jsr-88 separation of plans and
applications. I think we should restrict hot deploy to deploying
archaic applications with plans inside the application.
I agree with all that you said here DJ...except the not altering of
stuff in the directory. I think we are going to run a huge risk of
getting the config store and hot-deploy out of sync.
Just MNSHO :-)
thanks
david jencks
geir
IMHO, this dir should be for hot deploy only. Let the deployer
decide if it should be updated or added. I think the deletions
should not be done through this dir. We should use the normal
undeploy capabilities of the deployer.
Jacek
