[jira] [Resolved] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs
[
https://issues.apache.org/jira/browse/FOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Persson resolved FOP-2523.
Resolution: Invalid
The solution to fix the changed behavior of fop 2.x is to make sure there is a
correct configuration file. It seems that fop 1.0 had different default values
for the "base" URI in case no configuration was found.
To solve this problem one only has to setup a minimum fop configuration file as:
./
and the run fop with the "-c" option to specify this config file unless one
puts it in one of the default location where fop looks for it.
Will close this issue as it is not an issue (perhaps it should be mentioned in
some "gotchas" when moving from fop 1.1 to fop 2.x)
> Behavior change in include path handling breaks existing 1.1 docs
> -
>
> Key: FOP-2523
> URL: https://issues.apache.org/jira/browse/FOP-2523
> Project: FOP
> Issue Type: Bug
> Components: image/jpeg, image/png
>Affects Versions: 2.0
> Environment: OS X , Linux
>Reporter: Johan Persson
>Priority: Minor
> Labels: path
>
> When transforming a document with included files (images) there is a
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing
> build schemas due to fop making different assumption on relative paths in 1.1
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say,
> {{}}
> If all files (both images and .fo) are in a flat directory this works well
> with 1.1. Running the same source through 2.0 will generate an error saying
> that FOP cannot find the referred file (myimage.jpg)
> I suspect this is a common enough pattern to warrant some notice on how to
> handle this situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs
[
https://issues.apache.org/jira/browse/FOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Persson closed FOP-2523.
--
> Behavior change in include path handling breaks existing 1.1 docs
> -
>
> Key: FOP-2523
> URL: https://issues.apache.org/jira/browse/FOP-2523
> Project: FOP
> Issue Type: Bug
> Components: image/jpeg, image/png
>Affects Versions: 2.0
> Environment: OS X , Linux
>Reporter: Johan Persson
>Priority: Minor
> Labels: path
>
> When transforming a document with included files (images) there is a
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing
> build schemas due to fop making different assumption on relative paths in 1.1
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say,
> {{}}
> If all files (both images and .fo) are in a flat directory this works well
> with 1.1. Running the same source through 2.0 will generate an error saying
> that FOP cannot find the referred file (myimage.jpg)
> I suspect this is a common enough pattern to warrant some notice on how to
> handle this situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs
[
https://issues.apache.org/jira/browse/FOP-2523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15862925#comment-15862925
]
Johan Persson commented on FOP-2523:
The solution to fix the changed behavior of fop 2.x is to make sure there is a
correct configuration file. It seems that fop 1.0 had different default values
for the "base" URI.
To solve this problem one only has to setup a minimum fop configuration file
as:
./
and the run fop with the "-c" option to specify this config file unless one
puts it in one of the default location where fop looks for it.
Will close this issue as it is not an issue (perhaps it should be mentioned in
some "gotchas" when moving from fop 1.1 to fop 2.x)
> Behavior change in include path handling breaks existing 1.1 docs
> -
>
> Key: FOP-2523
> URL: https://issues.apache.org/jira/browse/FOP-2523
> Project: FOP
> Issue Type: Bug
> Components: image/jpeg, image/png
>Affects Versions: 2.0
> Environment: OS X , Linux
>Reporter: Johan Persson
>Priority: Minor
> Labels: path
>
> When transforming a document with included files (images) there is a
> different behavior between 1.1 and 2.x.
> Transformation that works with fop 1.1 no longer works with 2.0
> I suspect that this is not so much a bug as a change that breaks existing
> build schemas due to fop making different assumption on relative paths in 1.1
> compared with 2.x. but I have to yet figure out what the assumption is.
> If the generated .fo includes say,
> {{}}
> If all files (both images and .fo) are in a flat directory this works well
> with 1.1. Running the same source through 2.0 will generate an error saying
> that FOP cannot find the referred file (myimage.jpg)
> I suspect this is a common enough pattern to warrant some notice on how to
> handle this situation.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (FOP-2523) Behavior change in include path handling breaks existing 1.1 docs
Johan Persson created FOP-2523:
--
Summary: Behavior change in include path handling breaks existing
1.1 docs
Key: FOP-2523
URL: https://issues.apache.org/jira/browse/FOP-2523
Project: FOP
Issue Type: Bug
Components: image/jpeg, image/png
Affects Versions: 2.0
Environment: OS X , Linux
Reporter: Johan Persson
Priority: Minor
When transforming a document with included files (images) there is a different
behavior between 1.1 and 2.x.
Transformation that works with fop 1.1 no longer works with 2.0
I suspect that this is not so much a bug as a change that breaks existing build
schemas due to fop making different assumption on relative paths in 1.1
compared with 2.x. but I have to yet figure out what the assumption is.
If the generated .fo includes say,
{{}}
If all files (both images and .fo) are in a flat directory this works well with
1.1. Running the same source through 2.0 will generate an error saying that FOP
cannot find the referred file (myimage.jpg)
I suspect this is a common enough pattern to warrant some notice on how to
handle this situation.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0
[
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694960#comment-14694960
]
Johan Persson commented on FOP-2511:
I can confirm that the bug is fixed in the 20150812 snapshot. The PDF is
correctly produced.
Thanks!
Null pointer exception when transforming to PDF with FOP 2.0
Key: FOP-2511
URL: https://issues.apache.org/jira/browse/FOP-2511
Project: FOP
Issue Type: Bug
Affects Versions: 2.0
Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
Labels: fop, nullpointer
When trying to transform to PDF I'm experiencing a NULL pointer exception.
See below. The same fo-file used as source works without problem with FOP 1.1
The source for the fo-file is a set of DocBook 5 sources transformed using
XSLTproc. The fo-file that produces the crash can be found at my Google-Drive
at:
https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
{{java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
at
[jira] [Resolved] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0
[
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Johan Persson resolved FOP-2511.
Resolution: Duplicate
Fix Version/s: trunk
Fixed by the patch for https://issues.apache.org/jira/browse/FOP-2461
Null pointer exception when transforming to PDF with FOP 2.0
Key: FOP-2511
URL: https://issues.apache.org/jira/browse/FOP-2511
Project: FOP
Issue Type: Bug
Affects Versions: 2.0
Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
Labels: fop, nullpointer
Fix For: trunk
When trying to transform to PDF I'm experiencing a NULL pointer exception.
See below. The same fo-file used as source works without problem with FOP 1.1
The source for the fo-file is a set of DocBook 5 sources transformed using
XSLTproc. The fo-file that produces the crash can be found at my Google-Drive
at:
https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
{{java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
at
[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0
[
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14694333#comment-14694333
]
Johan Persson commented on FOP-2511:
I tried to find one of the nightly builds but the page seems to be missing the
builds.
https://ci.apache.org/projects/xmlgraphics/fop/snapshots/
The table headers seems to be there but no actual tar-balls to download.
Any ides where I can find a nightly build? (I guess I can try to put together
the necessary files directly from the SVN-repo but it would surely save some
time to have a pre-built-binary)
Null pointer exception when transforming to PDF with FOP 2.0
Key: FOP-2511
URL: https://issues.apache.org/jira/browse/FOP-2511
Project: FOP
Issue Type: Bug
Affects Versions: 2.0
Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
Labels: fop, nullpointer
When trying to transform to PDF I'm experiencing a NULL pointer exception.
See below. The same fo-file used as source works without problem with FOP 1.1
The source for the fo-file is a set of DocBook 5 sources transformed using
XSLTproc. The fo-file that produces the crash can be found at my Google-Drive
at:
https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
{{java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at
[jira] [Commented] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0
[
https://issues.apache.org/jira/browse/FOP-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14693361#comment-14693361
]
Johan Persson commented on FOP-2511:
I will pull down the trunk and try it out. Will take a day to two though.
Null pointer exception when transforming to PDF with FOP 2.0
Key: FOP-2511
URL: https://issues.apache.org/jira/browse/FOP-2511
Project: FOP
Issue Type: Bug
Affects Versions: 2.0
Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
Labels: fop, nullpointer
When trying to transform to PDF I'm experiencing a NULL pointer exception.
See below. The same fo-file used as source works without problem with FOP 1.1
The source for the fo-file is a set of DocBook 5 sources transformed using
XSLTproc. The fo-file that produces the crash can be found at my Google-Drive
at:
https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
{{java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
at
[jira] [Created] (FOP-2511) Null pointer exception when transforming to PDF with FOP 2.0
Johan Persson created FOP-2511:
--
Summary: Null pointer exception when transforming to PDF with FOP
2.0
Key: FOP-2511
URL: https://issues.apache.org/jira/browse/FOP-2511
Project: FOP
Issue Type: Bug
Affects Versions: 2.0
Environment: OS X 10.9.5 . Tested both with JDK 1.7.0_45 and JDK 1.6.0
Reporter: Johan Persson
Priority: Critical
When trying to transform to PDF I'm experiencing a NULL pointer exception. See
below. The same fo-file used as source works without problem with FOP 1.1
The source for the fo-file is a set of DocBook 5 sources transformed using
XSLTproc. The fo-file that produces the crash can be found at my Google-Drive
at:
https://drive.google.com/folderview?id=0BypRwfn2A3s6fnN6NW1PU1BEd3JiTzdyYlg0NjZxRTNFbFhUM21UMmw1ZUNjRGlYb1c2T28usp=sharing
{{java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:288)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:115)
at org.apache.fop.cli.Main.startFOP(Main.java:186)
at org.apache.fop.cli.Main.main(Main.java:217)
Caused by: java.lang.NullPointerException
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getCombinedKnuthElementsForListItem(ListItemLayoutManager.java:405)
at
org.apache.fop.layoutmgr.list.ListItemLayoutManager.getNextKnuthElements(ListItemLayoutManager.java:326)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:498)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.list.ListBlockLayoutManager.getNextKnuthElements(ListBlockLayoutManager.java:103)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:239)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
at
org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:289)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
at
org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextChildElements(FlowLayoutManager.java:223)
at
org.apache.fop.layoutmgr.FlowLayoutManager.addChildElements(FlowLayoutManager.java:147)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:116)
at
org.apache.fop.layoutmgr.FlowLayoutManager.getNextKnuthElements(FlowLayoutManager.java:69)
at
org.apache.fop.layoutmgr.PageBreaker.getNextKnuthElements(PageBreaker.java:252)
at
org.apache.fop.layoutmgr.AbstractBreaker.getNextBlockList(AbstractBreaker.java:643)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:178)
at
org.apache.fop.layoutmgr.PageBreaker.getNextBlockList(PageBreaker.java:158)
at
org.apache.fop.layoutmgr.AbstractBreaker.doLayout(AbstractBreaker.java:384)
at org.apache.fop.layoutmgr.PageBreaker.doLayout(PageBreaker.java:112)
at
org.apache.fop.layoutmgr.PageSequenceLayoutManager.activateLayout(PageSequenceLayoutManager.java:138)
at
org.apache.fop.area.AreaTreeHandler.endPageSequence(AreaTreeHandler.java:267)
at
org.apache.fop.fo.pagination.PageSequence.endOfNode(PageSequence.java:130)
at
org.apache.fop.fo.FOTreeBuilder$MainFOHandler.endElement(FOTreeBuilder.java:360)
at org.apache.fop.fo.FOTreeBuilder.endElement(FOTreeBuilder.java:190)
at
org.apache.xalan.transformer.TransformerIdentityImpl.endElement(TransformerIdentityImpl.java:1101)
at
[jira] [Closed] (FOP-2243) Typo in /usr/bin/fop breaks fop
[ https://issues.apache.org/jira/browse/FOP-2243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Johan Persson closed FOP-2243. -- Resolution: Invalid Fixed in patch update for OpenSuSE 12.3 Typo in /usr/bin/fop breaks fop - Key: FOP-2243 URL: https://issues.apache.org/jira/browse/FOP-2243 Project: Fop Issue Type: Bug Components: general Affects Versions: 1.1 Environment: OpenSuSE 12.3 Reporter: Johan Persson Original Estimate: 10m Remaining Estimate: 10m In the /usr/bin/fop start script there is a list of needed jars. Among them it is listed so: xml-commons-jaxp-1.3.apis There is s typo in this since the installed jar is actually named xml-commons-jaxp-1.3-apis The error is that there should be a hyphen (-) instead of a period after the version number. Reproducible: Always The fix is obvious correct the name of the JAR. Patch below. fop.OLD is the existing fop with error --- /usr/bin/fop.OLD2013-04-25 13:31:30.614395317 +0200 +++ /usr/bin/fop2013-04-25 13:31:56.952600172 +0200 @@ -33,7 +33,7 @@ # Rest of the configuration MAIN_CLASS=org.apache.fop.cli.Main -BASE_JARS=xmlgraphics-fop xmlgraphics-commons commons-logging commons-io avalon-framework batik-all xml-commons-jaxp-1.3.apis xml-commons-jaxp-1.3-apis-ext +BASE_JARS=xmlgraphics-fop xmlgraphics-commons commons-logging commons-io avalon-framework batik-all xml-commons-jaxp-1.3-apis xml-commons-jaxp-1.3-apis-ext # Set parameters set_jvm -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (FOP-2243) Typo in /usr/bin/fop breaks fop
Johan Persson created FOP-2243: -- Summary: Typo in /usr/bin/fop breaks fop Key: FOP-2243 URL: https://issues.apache.org/jira/browse/FOP-2243 Project: Fop Issue Type: Bug Components: general Affects Versions: 1.1 Environment: OpenSuSE 12.3 Reporter: Johan Persson In the /usr/bin/fop start script there is a list of needed jars. Among them it is listed so: xml-commons-jaxp-1.3.apis There is s typo in this since the installed jar is actually named xml-commons-jaxp-1.3-apis The error is that there should be a hyphen (-) instead of a period after the version number. Reproducible: Always The fix is obvious correct the name of the JAR. Patch below. fop.OLD is the existing fop with error --- /usr/bin/fop.OLD2013-04-25 13:31:30.614395317 +0200 +++ /usr/bin/fop2013-04-25 13:31:56.952600172 +0200 @@ -33,7 +33,7 @@ # Rest of the configuration MAIN_CLASS=org.apache.fop.cli.Main -BASE_JARS=xmlgraphics-fop xmlgraphics-commons commons-logging commons-io avalon-framework batik-all xml-commons-jaxp-1.3.apis xml-commons-jaxp-1.3-apis-ext +BASE_JARS=xmlgraphics-fop xmlgraphics-commons commons-logging commons-io avalon-framework batik-all xml-commons-jaxp-1.3-apis xml-commons-jaxp-1.3-apis-ext # Set parameters set_jvm -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
