Making sure your documents work with XF Ultrascale

   XF Ultrascale is able to process input documents of any size because content is discarded immediately when is no longer needed. In order to be able to do that however, there is 1 simple rule that must be followed in all XSL-FO documents:

Repeated content must be available in advance.

Headers and footers must be defined before document’s body (all fo:static-content before fo:flow). Similarly, table headers and footers must be defined before table’s body.

If you can't ensure this rule, you can set PreloadDocument in RequestParameters to true.

In this case the entire document will be preloaded, which will result is a higher memory consumption and possibly, less scalability.  

Edited by admin - 02 Dec 2009 at 12:10am

Author	Message / View First Unread Post Share Topic Printable Version Delicious Digg Facebook Furl Google Boomarks Google Buzz MySpace Newsvine reddit StumbleUpon Translate Twitter Windows Live Yahoo Bookmarks Topic Search Topic Options Post Reply Create New Topic
gabig Members Profile Send Private Message Find Members Posts Add to Buddy List Admin Group Joined: 06 Aug 2008 Posts: 144	Post Options Post Reply Quote gabig Report Post Quote Reply Topic: Making sure your documents work with XF Ultrascale Posted: 06 Aug 2008 at 10:28am
	XF Ultrascale is able to process input documents of any size because content is discarded immediately when is no longer needed. In order to be able to do that however, there is 1 simple rule that must be followed in all XSL-FO documents: Repeated content must be available in advance. Headers and footers must be defined before document’s body (all fo:static-content before fo:flow). Similarly, table headers and footers must be defined before table’s body. If you can't ensure this rule, you can set PreloadDocument in RequestParameters to true. In this case the entire document will be preloaded, which will result is a higher memory consumption and possibly, less scalability. Edited by admin - 02 Dec 2009 at 12:10am