| Key: |
CDV-569
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
2 Major
|
| Assignee: |
Hung Huynh
|
| Reporter: |
Gary Keim
|
| Votes: |
0
|
| Watchers: |
1
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Severity: |
3 Feature failure (but usable), workaround available
|
| Fix In Branch: |
2.6, trunk
|
| Target: |
Pacheco
|
| Fixed In Revision: |
8232 (trunk)
|
| Date of First Response: |
17/Apr/08 08:29 AM
|
|
When using Spring in a default Tomcat webapp (ROOT), TC Spring doesn't properly determine the application name because com.tcspring.ApplicationHelper assumes a webapp classloader name will end with a non-empty context-path. When the ROOT webapp is used the context-path is empty and it mistakenly sets appName to the classloader name's prefix, such as "Tomcat.shared."
The workaround is to either not use a default webapp, but rather give it a non-empty context-path, or specify the wildcard jee-application name="*".
|
|
Description
|
When using Spring in a default Tomcat webapp (ROOT), TC Spring doesn't properly determine the application name because com.tcspring.ApplicationHelper assumes a webapp classloader name will end with a non-empty context-path. When the ROOT webapp is used the context-path is empty and it mistakenly sets appName to the classloader name's prefix, such as "Tomcat.shared."
The workaround is to either not use a default webapp, but rather give it a non-empty context-path, or specify the wildcard jee-application name="*".
|
Show » |
|
TC Spring incorrectly handling default (ROOT) webapp