Ales Justin wrote:
It means that the "deployment" wasn't successfully deployed.
Yes, it wasn't successfully deployed and hence I would expect immediate undeploy() :)
Ales Justin wrote:
I would say it's the visitors fault that the current deployment doesn't get properly cleaned up after error.
Consider this:
deploy()
{
doMyWork();
callThirdPartyCodeWhichCanEndUpThrowingThrowableOrRunTimeException();
}
Surely, my deployer/visitor isn't expected to catch Throwable and cleanup whatever I did in doMyWork(), or is it?