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=32671>. 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=32671 Summary: "fo:text with no fo:block ancestor" when using fo:title Product: Fop Version: 1.0dev Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When using <fo:title>foo</fo:title> (which seems perfectly legal), FOP dies with a NullPointerException after giving the message "Unexpected: fo:text with no fo:block ancestor". The exception is raised in org.apache.fop.fo.FOText.createBlockPointers(FOText.java:199), which tries to find a fo:block ancestor, gives the "Unexpected" message when it reaches Root, and then loops back and gets a NullPointerException. Inserting a "break;" after the "Unexpected" message instead gives a ClassCastException at org.apache.fop.layoutmgr.ContentLayoutManager.addChildLM(ContentLayoutManager.java:287), where it tries to add an org.apache.fop.layoutmgr.InlineStackingLayoutManager, which isn't an InlineLevelLayoutManager. I'll add an attachment with sample code. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
