I finally manged to bypass the problem after substituting the DOCTYPE in skinconf.xml: <!DOCTYPE skinconfig PUBLIC "-//APACHE//DTD Skin Configuration V0.7-1//EN" "http://forrest.apache.org/dtd/skinconfig-v07-1.dtd";>
with <!DOCTYPE skinconfig PUBLIC "-//APACHE//DTD Skin Configuration V0.7-1//EN" "C:\apache-forrest-0.7\main\webapp\resources\schema\dtd/skinconfig-v07-1.dtd"> That is, pointing to a local resource. It seems that somehow the xml-catalog does not really do its job here? I am behind a firewall and I have set the proxy properties which makes it even more curious. Regards Lars Bjerges ________________________________ Från: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Skickat: ti 2/28/2006 7:58 Till: user@forrest.apache.org Ämne: UnknownHostException Hi all. I just ran into a frustrating problem when trying to do a "forrest war" (or webapp) generation. This is forrest 0.7. When the skinconf.xml file is to be processed I get: load-project-props: Processing C:\forrest\sdfii\src\documentation\skinconf.xml to C:\forrest\sdfii\build\tmp\no-doctype-project-skinconf.xml Loading stylesheet C:\apache-forrest-0.7\main\webapp\resources\stylesheets\strip-doctype.xsl Warning: catalogpath listing external catalogs will be ignored: Fatal Error! java.net.UnknownHostException: forrest.apache.org Cause: java.net.UnknownHostException: forrest.apache.org Failed to process C:\forrest\sdfii\src\documentation\skinconf.xml BUILD FAILED C:\apache-forrest-0.7\main\forrest.build.xml:277: Fatal error during transformation This does not happen when I do a "forrest site" or "forrest run". I am behind a fire-wall but has set up the proxy-properties in my (project) forrest.properties (i.e. proxy.host, proxy.port, proxy.user and proxy.password) Furthermore I was under the impression that forrest uses local DTD/Schemas (via XML catalogue) and I tried to increase the verbosity (to 10) but nothing changed. I also checked the log4j.xml and tried to enable the ConsoleAppender but did not get any output at all. I would like to get rid of the Warning message: "catalogpath listing external catalogs will be ignored" that I really don´t understand but have a feeling that it might be a cause of the problem. Has anyone seen this type of problem before? Regards Lars Bjerges
<<winmail.dat>>
