|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 3482 | minor | always | 05-06-09 09:46 | 05-06-09 19:33 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | ferg | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | |||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.1 | ||
|
|
|||||
| Summary: | 0003482: web-app versioning with ROOT | ||||
| Description: |
(rep by sibyj) I've turned on web-app versioning using: 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 | |||||
|
|
|||||
|
|
||||