You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Jeanfrancois Arcand <jf...@apache.org> on 2002/11/14 17:31:08 UTC
Xerces 2.2.x & Struts 1.0.2 problem.
Hi,
finally, with the help of Craig, I was able to isolate the problem
Tomcat have with Xerces 2.2.x. When you have an <!ELEMENT line longer
that 80 characters in a DTD, Xerces 2.2.x thrown the misleading
exception everybody have seen.
In our case, file web-app_2_3.dtd included with Struts 1.0.2 is causing
the problem (Strangely, this is not the same as the web-app_2_3.dtd
included in jakarta-servletapi). Struts 1.1 have a 80 characters format.
We have 3 solutions:
(1) Bundles Struts 1.1 latest build with Tomcat 4.1.x
(2) Compile Struts 1.0.2 with our version of web-app_2_3.xml and commit
the jar file in the webapp WEB-INF/lib folder.
(3) Wait for a new release of Xerces (or when the fix will be available).
The bugzilla bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282
This bug was difficult to isolate :-)
-- Jeanfrancois
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Xerces 2.2.x & Struts 1.0.2 problem.
Posted by Remy Maucherat <re...@apache.org>.
Jeanfrancois Arcand wrote:
> Hi,
>
> finally, with the help of Craig, I was able to isolate the problem
> Tomcat have with Xerces 2.2.x. When you have an <!ELEMENT line longer
> that 80 characters in a DTD, Xerces 2.2.x thrown the misleading
> exception everybody have seen.
Great ! (Craig saves the day again :) )
> In our case, file web-app_2_3.dtd included with Struts 1.0.2 is causing
> the problem (Strangely, this is not the same as the web-app_2_3.dtd
> included in jakarta-servletapi). Struts 1.1 have a 80 characters format.
>
> We have 3 solutions:
Ok, the following is just IMO.
> (1) Bundles Struts 1.1 latest build with Tomcat 4.1.x
I would rather not.
> (2) Compile Struts 1.0.2 with our version of web-app_2_3.xml and commit
> the jar file in the webapp WEB-INF/lib folder.
I don't like it either.
> (3) Wait for a new release of Xerces (or when the fix will be available).
I would choose that one.
I haven't updated my set of binaries at all to build 4.1.15 (the
rationale is: why upgrade when everything works fine ?). I plan to do
some conservative upgrading for the next build, including:
- Xerces 2.2.2 (if out by then)
- MX4J 1.1.1
- Beanutils 1.5
- Collections 2.1
> The bugzilla bug: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282
>
> This bug was difficult to isolate :-)
I suppose. The reported error was Microsoftian ;-)
Remy
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Xerces 2.2.x & Struts 1.0.2 problem.
Posted by Henri Gomez <hg...@apache.org>.
Jeanfrancois Arcand wrote:
> Hi,
>
> finally, with the help of Craig, I was able to isolate the problem
> Tomcat have with Xerces 2.2.x. When you have an <!ELEMENT line longer
> that 80 characters in a DTD, Xerces 2.2.x thrown the misleading
> exception everybody have seen.
>
> In our case, file web-app_2_3.dtd included with Struts 1.0.2 is causing
> the problem (Strangely, this is not the same as the web-app_2_3.dtd
> included in jakarta-servletapi). Struts 1.1 have a 80 characters format.
>
> We have 3 solutions:
>
> (1) Bundles Struts 1.1 latest build with Tomcat 4.1.x
> (2) Compile Struts 1.0.2 with our version of web-app_2_3.xml and commit
> the jar file in the webapp WEB-INF/lib folder.
> (3) Wait for a new release of Xerces (or when the fix will be available).
The pragmatic way should be to ask for a struts 1.0.2a release including
the correct web-app_2_3.xml ;)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>