I can only repeat myself: Is the error message here really the only message
in FOP's output?

To isolate the problem further you can just generate the FO file in your
application and stream that to a file. Then run that FO file through FOP
from the command-line. If it works that way, you probably have a
namespace problem in your code (which should show up as error message in
FOP's log output).

On 04.03.2008 13:06:41 Fournier,Danny [NCR] wrote:
> First thank you both Jeremias and Miroslav. Getting rid of the border
> did fix it at my end too - well, for the example file I initially sent.
> 
> However, after applying the same fix to my original file, I get the same
> error. There must be some markup that is not supported thus throwing
> this generic error?. I'll try to find a validator that could potentially
> shed some light on this. I usually just put the FO file in XML Spy and
> it would indicate to me what was wrong. So far, it doesn't complain at
> this FO though.
> 
> @Jeremias Maerki:
> 
> I'm using Coldfusion to generate the XML, and read in an XSL file that I
> created in XMLSpy. I then pass those two variables stored in memory to
> my custom FOP class which accepts these sorts of parameters.
> 
> Here's a snippet:
> 
> public String setXSLT(String strXSLT){
>       try{
>               this.xslt = new
> ByteArrayInputStream(strXSLT.getBytes("ISO-8859-1"));
>               return "";      
>                       
>       }
>       catch(UnsupportedEncodingException uee){                        
>               return getStackTrace(uee);
>       }       
> }
> 
> @Miroslav Pukhalsky
> 
> I am using 0.94. Not sure if this makes any difference?
> 
> Thanks again to all.
> 
> Dan
> 
> > -----Original Message-----
> > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] 
> > Sent: March 4, 2008 2:56 AM
> > To: [email protected]
> > Subject: Re: fo:simple-page-master is missing child elements
> > 
> > Hmm, I cannot reproduce the error with your example file. I 
> > get an error,
> > though: you specified a border on region-body which is not 
> > allowed by the spec. But if I remove the border, everything 
> > is fine. Shrug.
> > 
> > Are you using a peculiar XML parsing setup? Maybe the 
> > generated FO looks ok (if it is serialized to a file), but 
> > FOP does not receive the SAX events with the proper namespace 
> > information. Is the error message here really the only 
> > message in FOP's output?
> > 
> > On 03.03.2008 20:14:34 Fournier,Danny [NCR] wrote:
> > > Thanks Jay and Andreas.
> > > 
> > > What if I keep getting errors even though I have the 
> > minimalistic of FO?
> > > 
> > > fo:root is missing child elements. 
> > > Required Content Model: (layout-master-set, declarations?, 
> > > bookmark-tree?, page-sequence+)
> > > 
> > > <fo:root xmlns:fo="http://www.w3.org/1999/XSL/Format";>
> > > 
> > >   <fo:layout-master-set>
> > >           <fo:simple-page-master page-width="8.5in"
> > > page-height="11in" master-name="myPages">
> > >                   <fo:region-body margin-right="0mm"
> > > margin-left="0mm" margin-bottom="0mm" margin-top="0mm"/>
> > >           </fo:simple-page-master>
> > >           <fo:simple-page-master page-width="8.5in"
> > > page-height="11in" master-name="inventoryPages">
> > >                   <fo:region-body border="0.5pt solid #000"
> > > margin-right="8mm" margin-left="7mm" margin-bottom="41mm"
> > > margin-top="24mm"/>
> > >                   <fo:region-before display-align="after"
> > > extent="24mm" region-name="header"/>
> > >                   <fo:region-after display-align="before"
> > > extent="41mm" region-name="footer"/>
> > >           </fo:simple-page-master>
> > >   </fo:layout-master-set>
> > > 
> > >   <fo:page-sequence master-reference="myPages">
> > >           <fo:flow flow-name="xsl-region-body">
> > >                   <fo:block>Body</fo:block>
> > >           </fo:flow>
> > >   </fo:page-sequence>
> > > 
> > > 
> > > 
> > >   <fo:page-sequence master-reference="inventoryPages">
> > >   
> > >           <fo:static-content flow-name="header">
> > >                   <fo:block>Header</fo:block>
> > >           </fo:static-content>
> > >           
> > >           <fo:static-content flow-name="footer">
> > >                   <fo:block>Footer</fo:block>
> > >           </fo:static-content>
> > >           
> > >           <fo:flow flow-name="xsl-region-body">
> > >                   <fo:block>Body</fo:block>
> > >           </fo:flow>
> > >   </fo:page-sequence>
> > >   
> > > </fo:root>
> > > 
> > > I've gone through this document for the past 30 minutes trying to 
> > > identify the problem. Maybe I should address my questions 
> > to an XSL-FO 
> > > markup list instead?
> > > 
> > > Dan
> > <snip/>
> > 
> > 
> > Jeremias Maerki
> > 



Jeremias Maerki


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to