Details
-
Bug
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.5
-
None
-
None
Description
A call to FObj.removeChild() when the actual FO object has only one child and no sibling results in a NullPointerException.
Attachments
Attachments
Issue Links
- is related to
-
FOP-2717 FOP 2.2 did not contain FOP-2300 patch
- Resolved