[
https://issues.apache.org/jira/browse/FOP-2276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14548495#comment-14548495
]
Andreas L. Delmelle commented on FOP-2276:
------------------------------------------
Seems like the only way to force execution of that line would be:
{code:language=java}
try {
// rest of method body
} finally {
currentFObj = currentFObj.getParent();
}
{code}
Sound about right? Or does anyone see another solution to this?
> currentFObj is not updated if Throwable is thrown
> -------------------------------------------------
>
> Key: FOP-2276
> URL: https://issues.apache.org/jira/browse/FOP-2276
> Project: Fop
> Issue Type: Bug
> Components: fo/unqualified
> Affects Versions: 1.1
> Reporter: Daniel Dracott
>
> If an exception is thrown during
> org.apache.fop.fo.FOTreeBuilder.MainFOHandler.endElement(String, String,
> String), then the line "currentFObj = currentFObj.getParent();" does not get
> executed. If the SAX event source decides to store the exception and
> continue, then subsequent endElement calls can generate SAXExceptions of the
> form:
> Caused by: org.xml.sax.SAXException: Mismatch: page-sequence
> (http://www.w3.org/1999/XSL/Format) vs. root
> (http://www.w3.org/1999/XSL/Format)
> at
> org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:338)
> at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:181)
> ...
> Some implementations of javax.xml.transform.Transformer that we have used
> will attempt to perform further endElement calls in this way and the
> SAXException can hide the original Throwable, making diagnosis of problems
> difficult.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
