On Wed, 14 Mar 2001, Miles Poindexter wrote:
> After upgrading from Tomcat 3.2.1 to 4.0 beta, the weird hang problems and Hotspot
>JVM fatal errors are gone!
> Here's some notes about the installation, and some possible bug info:
>
> One problem was this method:
> writer.write(s.getBytes());
>
> where "s" is a String object and "write" is an OutputStream. If s happened to be a
>blank string, then after calling this method, nothing more could be written to the
>output stream. Since our app is creating dynamic HTML pages this way (replacing
>dynamic tags and appending to the output stream, I was getting half finished pages.
>Could this be a Tomcat 4.0 bug? It did work on earlier versions I think.
>
It might be a bug. Could you please submit a bug report (with a small
test case) to our bug tracking system?
http://jakarta.apache.org/bugzilla/
> Also, just a note about the web.xml doc. I looked at one or two of the DTDs and
>there does not seem to be documentation about this:
> One must put all the <servlet> entries at the beginning of the xml doc, and then all
>the <servlet-mapping> entries at the end. If you try to mix the two type of entries
>the parser complains.
>
The DTDs actually do state the ordering requirement.
Up near the top of the DTD, do you see the line that starts:
<!ELEMENT webapp (icon?, display-name?, description?, ...
and so on? That line is stating that the optional <icon> element goes
first, followed by the optional <display-name> element, and so on. The
asterisk after entries like "servlet*" and "servlet-mapping*" state that
you can have zero or more of these elements, but they all have to appear
at that point in the XML file.
For further info on the DTDs, see the XML 1.0 spec.
Craig McClanahan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
