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-functional ContextSpecifier.ContextPath and complicated tree-structure nonsense completely unnecessary to implement such feature: http://marc.theaimsgroup.com/?l=tomcat-user&m=114436878122925&w=2 http://issues.apache.org/bugzilla/show_bug.cgi?id=34057 http://issues.apache.org/bugzilla/show_bug.cgi?id=35035 Message describing problems with possibly-related problems with Context Path specifiers. http://marc.theaimsgroup.com/?l=tomcat-user&m=113877278215302&w=2 Why is there any tree logic necessary? What is conceptually complicated with a Context Path specification, other than it being a simple String property of a Context object? -- granted that, in-memory, you might want a PATRICIA trie or somesuch to look them up; -- but to load/ store & specify them, tree structure complexity seems questionable. Why is there almost no simple, functioning, means to specify basic Context details? ???
