forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject Re: Fwd: FOP's Forrest-based web site
Date Fri, 05 Mar 2004 15:37:29 GMT
Clay Leeds wrote:
> I'm still having problems getting a 'clean' build of the FOP web site.  
> The problem is indicated below. I'd love to get past this little glitch  
> so the Apache FOP web site can bask in the glory of finally having a  
> "Full-Site PDF" link which works...
> 1. I get a BUILD FAILED error, with the following issues indicated in  
> the output:
> X [0]                       site.pdf    BROKEN:  
> java.lang.RuntimeException: java.lang.RuntimeException:  
> java.lang.RuntimeException: java.lang.RuntimeException:  
> java.lang.RuntimeException: org.apache.fop.apps.FOPException: The id  
> "design/" already exists in this  
> document

When creating the site PDF it aggregates all the pages together. If two 
pages have the same element ID then the resulting aggregate will have a 
duplicate ID which is illegal in XML.

> X [0]                       design/fonts.html   BROKEN:  
> /Users/Shared/_WebDLs/xml-fop/build/tmp/context/content/xdocs/design/ 
> fonts.xml (No such file or directory)

you refer to a fonts.xml file (probably as fonts.html) and there is no 
source file for it.

> X [0]                       useragent.html      BROKEN:  
> /Users/Shared/_WebDLs/xml-fop/build/tmp/context/content/xdocs/ 
> useragent.xml (No such file or directory)

see fonts.xml above

> X [0]                       design/extensions.html      BROKEN:  
> /Users/Shared/_WebDLs/xml-fop/build/tmp/context/content/xdocs/design/ 
> extensions.xml (No such file or directory)

see fonts.xml above

> I'm also curious about the following issue.
>> 2. Currently my site structure has two elements with the same name. 
>> Is  there a problem that I have two 'design' elements  
>> (/site/development/design & /site/design)? 


>> I was thinking of using  
>> indirect linking to resolve issues with links in the  
>> /site/development/design section (e.g., site:design).





View raw message