From: <[EMAIL PROTECTED]>
> I don't know why I'm wasting my bandwidth on this, but,...
I apologise for being a complete asshole yesterday :-/
I'll try my best to keep my personal emotional wavings off this list.
-oOo-
I've looked in the dbpoolx.mod file and don't understand what's the problem
too; assuming of course that with all those entities the line number
reported is correct.
I've taken a look in the Xerces lists and there's a pointer to the fact that
big DTDs like the DocBook one have a tendence to crash Xerces.
Anyway, you could do the following:
1. Try running the build locally setting the classes you need manually in
the CLASSPATH, using the latest Gump built jars of jakarta-ant xml-xerces
xml-xalan2 commons-httpclient jakarta-log4j jakarta-regexp jdom junit jaxen
xml-apis saxpath and setting the property build.sysclasspath to "only", so
that only the classes included in the classpath are used (like Gump does).
2. try disabling the Internet connection on your computer to see if the
error message it gets is similar to the one Gump gives.
3. place the whole DTD locally and change the reference in the XML file to
fetch it there.
4. Disable DTD fetching alltogether as described in
http://marc.theaimsgroup.com/?l=xerces-j-user&m=101896956402054&w=2 (not
recommended since DTDs are important)
In any case, run with -debug enabled to see what is really going on.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
