If the user deploys a web application with context path equal to a predeployed
web application, the original application is undeployed without the user being
noticed. This is ok if it is a redeployment of the same project; however it may
be bad if it is a different project just with context path collision.
The same issue applies to module names (ejb / web); and may also apply to
resources or web service endpoints.
A more severe variant of this issue is:
-> j2eeserver, tm -> 6.0
none of these TM values are valid at this point
Obviously this has not ever been reported by a real user.