context problems: incorrect auto-deploy of webapps when context specifiers exist

Hi people, Webapps with explicit Context specifiers in server.xml are not correctly recognized according to their docBase specifiers. Tomcat consequently incorrectly deploys duplicates of these apps under default context specifiers. For apps involving resources or non-trivial behaviour, eg

context problems: edit /conf/[engine]/[host]/someApp.xml scrubs app in /webapps

Hi people, Editing user-created Context specifiers in /conf/[engine]/[hostname], for webapps deployed as per traditional in /webapps, appears to incorrectly cause the webapp to be scrubbed with web.xml being deleted and the webapp becoming non-functional. No recovery is possible with manua

context problems: docBase inside the host appBase warnings

Hi people, Specifying a Context descriptor for a traditionally-deployed webapp, in /webapps, produces warnings when using the supposed 'new and recommended' /conf/[engine]/[hostname]/someApp.xml context specifiers. WARNING: A docBase XXX inside the host appBase has been specified, and wil

context problems: META-INF/context.xml context paths non-functional

Hi people, Posting a series of issues in Context Specifications and related areas. This area seems rather more troublesome than it should, so I think I need to go through all of these and make people aware of how much is going on in this area... Context specifiers placed within the webapp at

context problems: Context Path specifiers broken in TC 5.5

Hi people, Context Path specifiers seem substantially non-functional in the new deployer technology. Collection of bugs related to this area: Bug describing context paths in webapp META-INF/context.xml being ignored: http://issues.apache.org/bugzilla/show_bug.cgi?id=39120 Bugs describing non-

context problems: other threads on non-functional Context Specifiers

Hi people, Threads from other people describing non-functionality with Context Specifiers in 5.5 Reloading and JDBC specification problems with Context: http://groups.google.co.nz/group/comp.lang.java.programmer/browse_frm/thread/7016429627d389c9/2b95e1e1aa8d59ce?lnk=st&q=tomcat+5.5+contexts&r

context problems: not addressed; summary

Hi people, As posted thru this series, Context Specifiers (which should be conceptually trivial) seem to have become a problem area. To some extent Deployment also seems to be touched by this. I identify the problem as Design and lack of conceptual clarity, rather than code. We can see a la

prediction; context problems

Hi people, Sriram, Remy, Costin, Thanks Sriram for the +1 on this! As you guys have read, I think something is up in the the area of Context information; specifiers, parsing, and storage of current deployment state. I've previously been talking about determinism as one of the problems, but

re: Deployement of war and context.xml files

Hi Henri, Apparently /conf/Catalina/localhost is meant to represent the 'current deployed state' of contexts/ webapps deployed. So it's reasonable from this understanding, that the Context specifier file is deleted when you undeploy the app; the context is being removed from the 'current st

Re: Creating a context and deploying a new application on the fly.

Hi David, Looks like there may be a problem with your Context Resource code. >From your programmatic configuration: >ContextResource resource = new ContextResource(); >resource.setName("jdbc/reference"); >From your commented 'origin' example: >

re: context folders and Delete on tomcat root; funny [Bug 39594]

Hi people, Pedro, This is both a sad & funny true story. http://issues.apache.org/bugzilla/show_bug.cgi?id=39594 > We were trying to make our servlets use relative path so that our deplayment > would > be faster. In the process we try putting $Catalina_home in the path for the > base doc >