TC Spring incorrectly handling default (ROOT) webapp
----------------------------------------------------
Key: CDV-569
URL: https://jira.terracotta.org/jira//browse/CDV-569
Project: Community Development
Issue Type: Bug
Components: X-SpringRuntime
Affects Versions: 2.5.0
Reporter: Gary Keim
Assignee: Issue Review Board
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="*".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.terracotta.org/jira//secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
tc-dev mailing list
[email protected]
http://lists.terracotta.org/mailman/listinfo/tc-dev
