DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=13282

Xerces2-J 2.2.0 make tomcat 4.1.12 failed at init





------- Additional Comments From [EMAIL PROTECTED]  2002-11-14 01:36 -------
OK, I finally found what is the problem (with the help of Craig McClanahan).
Xerces 2.2.x fail with a wrong exception when you have a DTD that contains line
that have more than 80 characters.

The problem is something related to DTD having more than 80 characters. Remember
that the problem have started with Xerces 2.2.x. As an example, this will not fail:

<!ELEMENT web-app (icon?, display-name?, description?, distributable?,
context-param*, filter*, filter-mapping*, listener*, servlet*,
servlet-mapping*, session-config?, mime-mapping*, welcome-file-list?,
error-page*, taglib*, resource-env-ref*, resource-ref*, security-constraint*,
login-config?, security-role*, env-entry*, ejb-ref*,  ejb-local-ref*)>

but this will:

<!ELEMENT web-app (icon?, display-name?, description?,
distributable?,context-param*, filter*, filter-mapping*,
listener*,servlet*,servlet-mapping*, session-config?, mime-mapping*,
welcome-file-list?,error-page*, taglib*, resource-env-ref*,resource-ref*,
security-constraint*,login-config?, security-role*, env-entry*, ejb-ref*, 
ejb-local-ref*)>

The problem does not occurs if the line is a comments:

<!--
The auth-method element is used to configure the authentication
mechanism for the web application. As a prerequisite to gaining access to any
web resources which are protected by an authorization
constraint, a user must have authenticated using the configured
mechanism. Legal values for this element are "BASIC", "DIGEST",
"FORM", or "CLIENT-CERT".

will always parse properly.  The bug *only* occurs when with an <!ELEMENT....    >

Thanks and hope you will be able to fix the problem.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to