Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of ajmas@sympatico.ca designates
 65.55.111.111 as permitted sender)
Message-ID: <BLU0-SMTP948BEE14C9145D58319FF7C55F0@phx.gbl>
From: Andre-John Mas <ajmas@sympatico.ca>
To: "Tomcat Users List" <users@tomcat.apache.org>
In-Reply-To: <b18c6e3b0905150737s15e96b56jd720066b4e9a9921@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: tomcat no longer writing to log files
Date: Fri, 15 May 2009 11:00:21 -0400
References: <b18c6e3b0905141235s77ef1a74h58127019cbf06053@mail.gmail.com>
  <0AAE5AB84B013E45A7B61CB66943C17228D96D4EF8@USEA-EXCH7.na.uis.unisys.com>
  <b18c6e3b0905141442q78a69df6lff357801942b2d36@mail.gmail.com>
  <4A0D41D7.28724.6CC950CE@ochanis.ncc.edu>
 <b18c6e3b0905150737s15e96b56jd720066b4e9a9921@mail.gmail.com>


On 15-May-2009, at 10:37, Michael A. Repucci wrote:

>> Also, tomcat does work "out of the box". Incorrect administration =20
>> of any
>> system will stop it
>> from working out of the box.
>
>
> Honestly, what I'm most frustrated about isn't Tomcat, per say, but =20=

> the
> stuff written by my colleagues that should work with Tomcat. I'm a bit
> baffled how the =FCber-cross-platform Java (and its disciples Ant and =20=

> Tomcat)
> could be used to create code that is extraordinarily sensitive to the
> version and platforms on which it is compiled and run. I suppose =20
> that's just
> because the code was poorly written, and you could probably write =20
> platform-
> and version-dependent code in any language, but it would have been =20
> nice if I
> could have installed whatever the latest packages were on my system, =20=

> and
> compiled and run successfully the first time. Instead I'm spending =20
> upwards
> of a week learning all the internals. I guess that's useful in the =20
> long run,
> but I could just use some good and patient guidance. Sorry to have =20
> stepped
> on anybody's toes, and thank you all for your help.
>

I hate to say it, but the best way to make Java code have issues is =20
trying to
be too smart when doing something. This usually results in code that =20
works
in certain narrow situations, but not the rest. What I mean by being =20
'too
smart' is when someone try to make the best 'uber' code possible, =20
which ends
up being convoluted and only understandable to the author when it was
written. I am not saying it is the case here, but programming is like
hand writing, in that you do yourself a favour by making sure it is =20
written
well enough that someone else can read it and yourself in a month's =20
time.

On the other hand, there are different version of servlet specification,
of Java, of Tomcat and each has their incompatibilities. Learning how to
make your code work in the widest range of conditions will help make
you a better programmer, IMHO.

Andr=E9-John=

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org