John, I am in no way an expert on Tomcat, but I do know that some things are driven by the spec and not the developers. I am also sure that some things have come and gone in versions.
For feature one, I would submit a bug report on the documentation, not the software, and outline in detail as you have here. Some of the documentation is carried over from previous versions and fails to get updated when changes occur. Simply ask that a notation be added that the feature no longer functions after a certain version. Minor notes are often acted upon quicker than a major rewrite. As for feature two, this is a spec issue. To support 2.4 this feature was added. As for removal of the other feature I can only guess why it no longer remains, but my money would be on, its not by spec and thus Tomcat specific. It has been noted on the list several times that there are features that are not per spec and may be removed at any time. So the safe way to do things is to follow the spec. When one likes to be on the bleeding edge, one must be prepared to bleed at times. I do not mean to flame you in any way. Only to share my opinion. But, if you do consider a different package, you will still have to change your structure, because the other package will not support it either. Read the spec, feel the spec, be the spec. If you find something that does not follow the spec then, by all means let 'em have it! IMHO Delete at will. Doug ----- Original Message ----- From: "John H" <[EMAIL PROTECTED]> To: "Tomcat Users List" <[EMAIL PROTECTED]> Sent: Friday, April 23, 2004 2:37 PM Subject: A word of caution upgrading Tomcat > I hate to open a can of worms, but I see no other choice. Something needs to > be done about features that appear and disappear seemingly randomly between > versions. > > Here are a few examples. Despite what the documentation says (which may or > may not be accurate), these features really worked, and now don't. > > In TC 4.0.4, you could put <Resource> and <ResourceParams> directives in a > <DefaultContext>. This is no longer true in TC4.1.24, and you are forced to > put the <Resource> stuff in <GlobalNamingResources>, despite what the > documentation said (and still says) in > http://jakarta.apache.org/tomcat/tomcat-4.1-doc/config/defaultcontext.html > > In addition, in 4.1.24 you could put context descriptors (XML files > describing your context) in the appBase of your <Host>, and they would load. > In TC5.0.19 that feature has been removed, and you must now use META-INF or > [Catalina_home]/conf/<Engine>/<Host>. I've verified this in the code. > > I beleive that TC5 was branched at 4.1.7. If this feature was added post > 4.1.7, why did it not get integrated into the 5.0 tree? How many other post > 4.1.7 features/bug fixes have been left out? > > No one seems to care about these loss of features. For the second loss of > functionality above, I entered a bug in bugzilla which was promptly closed > and I was told to RTFM. I did RTFM, and while it is confusing, it does > indirectly say I can no longer do what I could in 4.1.24 (by telling me what > I CAN do). No mention of this feature's deprecation or any reason why (even > after I asked). Forgive me for not wanting to change my current structure, > especcially since I don't see any reason why it would change. > > I suppose I'll be flamed for complaining about a free product, but the > Apache organization, of which Tomcat is a member, is known for high quailty > open-source development. These missteps seem very out of character, and I > think the development team should address them, > > I hope that I'm not a lone in my feelings here. If I am, I'll gladly crawl > back into my hole and mumble under my breath, and perhaps consider another > JSP/Servlet container. > > Thanks for listening, > > John > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
