Bugs item #523464, was opened at 2002-02-27 08:52
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=523464&group_id=22866
Category: CatalinaBundle
Group: v3.0 Rabbit Hole
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Georg Schmid (giorgio42)
Assigned to: Scott M Stark (starksm)
Summary: Be online to deploy WAR,ValidateDTD ign.
Initial Comment:
Context:
RH beta 2 catalina bundle.
This is to some degree a clone of bug #465821.
I just read Andy Schaefer's comment on that. Hihi.
I saw a statement on the JDOM website that crimson is
always loading the DTD, even when not validating
(true?).
Replaced crimson by xerces. Now the stack trace tells
me, that it actually tries to validate the web.xml.
Which means ValidateDTDs setting is ignored.
Deployment used to work with Jetty without being
online. How are they reading the web.xml?
But I grew up with Tomcat...
Is there a portable way (across XML parses) to disable
DTD loading (the parser may ignore it anyway)?
Xerces has the load-external-dtd feature, which might
be good enough for a work-around.
Georg
----------------------------------------------------------------------
Comment By: Jason Robertson (jrslim)
Date: 2002-03-12 13:25
Message:
Logged In: YES
user_id=464997
I had similar problems in utility app, where I was using
JDOM. To solve it, I created a custom EntityResolver that
opened a resource (inside the .jar with the EntityResolver
class) for DTDs it recognizes. Just before opening a
document with a parser, you configure the parser to use the
custom EntityResolver and everything goes smoothly when
you're offline (or, in my case, behind a password-required
firewall).
Since JBoss has many applicable DTDs in the build structure
perhaps these could be included somewhere in the release
packaging (if they're not in a .jar somewhere already), and
with the proper tag in some conf file
("useLocalDTDs=true" ?) it could use the local ones for
resolving entities/validation.
As far as "disabling" DTD loading, the JDOM mailing list
folks explained that this would be "illegal" as entity
references may need to be expanded and this information is
in the DTD. So, even if you're not validating, if there is
a DOCTYPE tag in the document they require the loading of
the DTD.
I just checked the Xerces docs, and actually my
EntityResolver is a org.xml.sax.EntityResolver which will
work directly in Xerces. If anyone on the JBoss side wants
to help with the config part and the making JBoss use my
class part, I'll gladly donate the class.
Jason
----------------------------------------------------------------------
Comment By: Joao Pedro Clemente (jpcl)
Date: 2002-03-12 10:56
Message:
Logged In: YES
user_id=169196
I have this problem too, but with JBoss 2.4.4 + Tomcat 3.2.3.
Just to add to the count... This bug seems the same as
reported in #489465
----------------------------------------------------------------------
You can respond by visiting:
http://sourceforge.net/tracker/?func=detail&atid=376685&aid=523464&group_id=22866
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development
