https://issues.apache.org/bugzilla/show_bug.cgi?id=54808
--- Comment #2 from Mark Thomas <ma...@apache.org> --- I'm not convinced of the usefulness of this feature. The stated purpose is fall-back. Consider an application on version 1 and version 2 is deployed. If a system admin wants the ability to fall-back to version 1 if problems are noticed with version 2: - With this option implemented, falling back would require deleting version 2 which will break the session for every user currently using version 2. That may not be the desired behaviour. - Once version 2 is considered stable version 1 would need to be manually removed. This makes the undeployOldVersions feature unnecessary which in turn makes this feature unnecessary. Users wanting the ability to fall-back to version 1 after version 2 has been deployed would be better following a different process: - leave undeployOldVersions="true" - deploy version 2 - if fall back is required - deploy a copy of version 1 labelled as version 3 - delete version 2 if it is necessary to force users of version 2 I'd be happy to commit this new feature if there is a use case that cannot easily be met by the current features but fallback does not appear to be it. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
