On Wed, 2003-11-26 at 17:47, Timothy Larson wrote:
--- Geoff Howard <[EMAIL PROTECTED]> wrote:
Can someone try rolling back Xerces to prior version to make sure that's the issue? Of course, you'll have to unplug from the network before building or you won't notice the issue. I looked briefly at Xerces' site last night and didn't find any clues this was intentionally changed in the latest release but there were some bugfix descriptions which could point to an accidental new problem.
I retrieved old files via viewcvs: cocoon\2.1_20031125111946\cocoon-2.1\lib\endorsed\xercesImpl-2.5.0.jar (Rev 1.1) cocoon\2.1_20031125111946\cocoon-2.1\lib\endorsed\xml-apis.jar (Rev 1.4) cocoon\2.1_20031125111946\cocoon-2.1\tools\anttasks\XConfToolTask.java (Rev 1.8) and prepared for a clean build by deleting: cocoon\2.1_20031125111946\cocoon-2.1\build\cocoon-2.1.4-dev cocoon\2.1_20031125111946\cocoon-2.1\build\webapp cocoon\2.1_20031125111946\cocoon-2.1\lib\endorsed\xercesImpl-2.6.0.jar cocoon\2.1_20031125111946\cocoon-2.1\tools\anttasks\ManifestToolTask.class cocoon\2.1_20031125111946\cocoon-2.1\tools\anttasks\XConfToolTask.class but the clean build still produced the same UnknownHostException.
Aaaahhhh!!!!
If I unplug my network connection, I also get the UnkownHostException.
I reverted to xercesImpl-2.5.0.jar, left the rest the same, and now it works for me. So seems like a bug in Xerces to me.
I attempted directly using the DOMParser class directly as they recommend in the FAQ with mixed results. I've filed a bug with more details at Xerces bugzilla:
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=25043
I wasn't able to spend more time digging around or coming up with an isolated test case for them - any takers?
Geoff
