|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3466 | minor | always | 04-29-09 10:07 | 05-06-09 19:32 | |
|
|
|||||
| Reporter: | sibyj | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 3.2.1 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.1 | ||
|
|
|||||
| Summary: | 0003466: Resin 3.2.1 web-app versioning doesn't work with ROOT war file | ||||
| Description: |
I've turned on web-app versioning using: <web-app-deploy path="webapps" versioning="true"/> Its working great for non-ROOT named war files and will deploy and direct new user sessions to the newest version of the web-app, without having to restart Resin. For the ROOT web-app, however, I have to restart Resin in order for it to recognize the latest version i.e. If I copy an updated war into webapps like ROOT-1.2.2.war, it will deploy the war file but new user sessions are still directed to the old version. Is this functionality restricted to only non-ROOT web-apps or is this a bug? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||