[jira] [Commented] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17451334#comment-17451334 ] Roger Pilkey commented on FOP-3028: --- Works for me now when setting in the conf file. Thanks yet again, Simon, you da man. Roger > fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner updated FOP-3028: --- Summary: fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration fields (was: fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration fields) > fopFactoryBuilder.setConfiguration(fopConfig) ignores multiple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Resolved] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner resolved FOP-3028. Fix Version/s: trunk Resolution: Fixed http://svn.apache.org/viewvc?view=revision=1895426 > fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > Fix For: trunk > > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Assigned] (FOP-3028) fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration fields
[ https://issues.apache.org/jira/browse/FOP-3028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simon Steiner reassigned FOP-3028: -- Assignee: Simon Steiner > fopFactoryBuilder.setConfiguration(fopConfig) ignores mutliple configuration > fields > --- > > Key: FOP-3028 > URL: https://issues.apache.org/jira/browse/FOP-3028 > Project: FOP > Issue Type: Bug >Affects Versions: 2.3, 2.6 > Environment: Java 8-11, Windows 7-10 >Reporter: Martin Leitner >Assignee: Simon Steiner >Priority: Major > > As described in FOP-2524 (which was wrongly marked as Cannot Reproduce), you > can initialize the FopFactoryBuilder and provide a configuration as > InputStream, which works fine. > However, using fopFactoryBuilder.setConfiguration(config); will simply ignore > a number of configuration fields, among them source-resolution, > source-resolution, complex-scripts, accessibility. -- This message was sent by Atlassian Jira (v8.20.1#820001)
[jira] [Updated] (FOP-3035) NPE on combination of ZWSP, NBSP and
[
https://issues.apache.org/jira/browse/FOP-3035?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Steiner updated FOP-3035:
---
Summary: NPE on combination of ZWSP, NBSP and (was:
NullPointerException on combination of ZWSP, NBSP and )
> NPE on combination of ZWSP, NBSP and
>
>
> Key: FOP-3035
> URL: https://issues.apache.org/jira/browse/FOP-3035
> Project: FOP
> Issue Type: Bug
> Components: renderer/pdf
>Affects Versions: 2.6
> Environment: Linux SLES 11 running on Intel x86_64
>Reporter: Paul Katz
>Priority: Minor
> Attachments: bad.fo, fop-config.xml, fop.log
>
>
> The following line in my XSL:FO reliably causes a NPE when generating a PDF:
>
> {code:java}
> x {code}
> Removing any single element of this line makes the NPE go away:
>
> * The outer
> * {{The Zero-Width Space}}
> * The inner
> * The Non-Breaking Space
> * The "x" text
> (My actual document has more content within the outer ; I just
> removed everything else to provide the minimum content needed to reproduce
> the NPE.)
> The NPE is reported as:
>
> {code:java}
> SEVERE: Exception
> org.apache.fop.apps.FOPException
> java.lang.NullPointerException
> at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:296)
> at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:116)
> at org.apache.fop.cli.Main.startFOP(Main.java:183)
> at org.apache.fop.cli.Main.main(Main.java:214)
> Caused by: java.lang.NullPointerException
> ... {code}
>
> The complete FOP output is attached as fop.log.
> The complete input XSL:F0 is attached as bad.fo. The line of interest is near
> the bottom of the file. I have placed a comment above it listing several
> variations of the line with each element removed one at a time. Any of those
> alternatives prevents the NPE from occurring.
> My command line is:
>
> {noformat}
> fop/fop-2.6/fop/fop -c WD/fop-config.xml -fo bad.fo bad.pdf 2>&1 | tee
> fop.log{noformat}
> My FOP config file is attached as fop-config.xml.
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
