Steve Ochani wrote:
On 31 Mar 2006 at 19:34, Jay wrote:
I am pretty new to tomcat. I recently read a post
http://marc.theaimsgroup.com/?l=tomcat-user&m=114372017420869&w=2
which solved a problem I have been having for tomcat 5.5 also. I
thank that person for posting the solution. I also read some of the
responses from what appear to be the tomcat developers and was very
dissappointed. I also think that is a usability problem for newbs.
like tomcat team wants tomcat to only be usable for advanced users to
me. This frankly dissapoints me.
I disagree.
I don't know too many software products and their developers that help out regularly on
their support forums and e-mail lists.
Personally speaking (writing), as a developer (not for tomcat) and systems admin I notice
that most new people do not try to help themselves first. They don't bother to read any
documentation/instructions or hardly any at all and they don't bother to use a search
engine as google. On top of that a lot of these people, when they post questions, they do
not contain enough clear information for other people to help them.
Hopefully I don't fall into these types of newbies; I try to give as
much information as I can when asking a question. I also spend a lot of
time googling and reading the Tomcat docs before asking here, but I find
that the tomcat docs are far too general for a newbie like me to get
anything useful out of them. Also, in many cases, they talk more about
how things have changed from previous versions than they do about how to
use the current version. That's fine if you are used to an older
version, but someone who started with a recent version doesn't have much
of a starting place.
I guess this post is mostly a request for more description in the Tomcat
docs, particulaly of the type "If you want to do this, here's what
settings you put in and where", or "If you set this setting to this
value, here's what it does, and this is why you might (and might not)
want do to it that way". Sometimes, just an additional sentence or two
in the docs would have saved me hours of work and searching. For a
specific example, a few weeks ago I was asking about the caseInsensitive
settings for contexts. After much digging, I finally figured out that
it only applied to the individual resource name, and not the context
path; the fact that context paths are *always* case-sensitive (and in
fact, that is part of the spec) is never mentioned anywhere.
Thanks for listening,
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
