You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-dev@xmlgraphics.apache.org by bu...@apache.org on 2004/08/25 19:19:53 UTC
DO NOT REPLY [Bug 30851] New: -
[patch][enhancement] "No meaningful layout in block" --> better location in FOPException
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=30851>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=30851
[patch][enhancement] "No meaningful layout in block" --> better location in FOPException
Summary: [patch][enhancement] "No meaningful layout in block" -->
better location in FOPException
Product: Fop
Version: 0.20.5
Platform: Other
OS/Version: Other
Status: NEW
Severity: Enhancement
Priority: Other
Component: general
AssignedTo: fop-dev@xml.apache.org
ReportedBy: tagunov@motor.ru
While a new version of FOP is being designed and coded it would be highly benefitial to current FOP users to have
* more precise [systemId + line] reported when
FOP is unable to generate a layout
and endless loop terminator kicks in
* have getters for systemId, line, column on FOPException
In fact currently when FOPException with message
No meaningful layout in block after many attempts.
Infinite loop is assumed. Processing halted.
is thrown it may produce very little infromation that would help user
to locate offending fo element. In our case it contained line/column for
our fo:root element!
The proposed patch goes down FObj tree following markers and thus
locates offending fo element (a too large png imange in our case)
pretty well.
Also, while we're at it, getters for systemId, line, column on FOPException
are also helpful (we currently have to parse parse getMessage() ).