See [1]. Valid children of table-row are table-cell+.


On Fri, Jul 15, 2011 at 11:54 AM, Hamed Mohammed <> wrote:
I get this error intermittently while generating PDF report using FOP 1.0.
null:5511:928: "{}block" is not a valid child of "fo:table-row"! (See position 5511:928).  In most cases this issue is resolved on resubmitting the report. Can any one pin point what is the actual cause of this issue and why it is happening occasionally for the same input? "{}block" is not a valid child of "fo:table-row"! (See position 1143:945)

On Fri, Jul 15, 2011 at 9:42 AM, Chris Bowditch <> wrote:
On 12/07/2011 12:11, Glenn Adams wrote:
this is not a bug, as pointed out by Pascal

By debug I meant debug the XSLT/XSL-FO rather than the Java code.

On Tue, Jul 12, 2011 at 5:08 AM, Chris Bowditch < <>> wrote:

   On 12/07/2011 09:52, tecshine wrote:


       Thanks for the reply Pascal

       I have tried using fopFactory.setStrictValidation(false); but
       it doesnt
       solve the problem.
       Our entire application was based on FOP 0.20.5 and rewriting
       all XSLTs would
       mean a lot of work.
       Is there any other way we can resolve the issue.

   Can you generate the XSL-FO and post it to the list (if its not
   too big)

   Since you are submitting XSLT+XML to fop you will need to use
   -foout option when running FOP from the command line to generate
   the intermediate XSL-FO. We can debug the issue by looking at the



       Pascal Sancho wrote:

           Hi Swetha,

           FOP 1.0 is more strict than FOP 0.2x regarding the XSL-FO
           REC 1.1.
           Probably you will experiment further ValidationExceptions
           against FO
           elements or attributes (missing %block% in fo:table-cell
           is the most

           The best way is to rewrite your XSL-T to produce strict

           But FOP team offered a configuration tip to help in FOP
           0.2x to Latest
           migration: see [strict-validation] element at [1].


           Le 12/07/2011 08:14, tecshine a écrit :

               I have migrated from fop 0.20.5 to FOP 1.0. I get the
               following exception

               "fo:list-block" is missing child
               elements. Required content model: marker* (list-item)+
               (See position
               I am aware that this kind of errors occur when the
               parent is empty or
               have child elements, so check the xsl file .All
               "fo:list-block" elements
               the xsl file contain at least one  "fo:list-item"
               child element. Even
               then I
               stumble upon this exception.
               Can someone help me get out of this please.

               Thanks in advance

           --             Pascal

           To unsubscribe, e-mail:

           For additional commands, e-mail:

   To unsubscribe, e-mail:

   For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

Hamed Mohammed,