Build failed in Jenkins: xmlgraphics-fop-ant #265

2017-01-10 Thread Apache Jenkins Server 
See 

Changes:

[ssteiner] FOP-2362: Using Saxon to intermediate format throws 
NullPointerException

--
[...truncated 91 lines...]
  2100K .. .. .. .. .. 36% 41.7M 0s
  2150K .. .. .. .. .. 36% 62.8M 0s
  2200K .. .. .. .. .. 37% 50.9M 0s
  2250K .. .. .. .. .. 38% 53.7M 0s
  2300K .. .. .. .. .. 39% 1.91M 0s
  2350K .. .. .. .. .. 40% 66.7M 0s
  2400K .. .. .. .. .. 41% 58.3M 0s
  2450K .. .. .. .. .. 41% 76.9M 0s
  2500K .. .. .. .. .. 42% 63.1M 0s
  2550K .. .. .. .. .. 43% 32.8M 0s
  2600K .. .. .. .. .. 44%  100M 0s
  2650K .. .. .. .. .. 45% 90.6M 0s
  2700K .. .. .. .. .. 46% 53.5M 0s
  2750K .. .. .. .. .. 46% 68.0M 0s
  2800K .. .. .. .. .. 47% 58.7M 0s
  2850K .. .. .. .. .. 48% 74.2M 0s
  2900K .. .. .. .. .. 49% 58.3M 0s
  2950K .. .. .. .. .. 50% 79.5M 0s
  3000K .. .. .. .. .. 51% 74.7M 0s
  3050K .. .. .. .. .. 52% 58.4M 0s
  3100K .. .. .. .. .. 52% 84.9M 0s
  3150K .. .. .. .. .. 53% 72.7M 0s
  3200K .. .. .. .. .. 54% 70.4M 0s
  3250K .. .. .. .. .. 55% 60.2M 0s
  3300K .. .. .. .. .. 56% 72.1M 0s
  3350K .. .. .. .. .. 57% 67.3M 0s
  3400K .. .. .. .. .. 57%  101M 0s
  3450K .. .. .. .. .. 58% 69.7M 0s
  3500K .. .. .. .. .. 59% 57.5M 0s
  3550K .. .. .. .. .. 60% 57.2M 0s
  3600K .. .. .. .. .. 61% 74.0M 0s
  3650K .. .. .. .. .. 62% 64.3M 0s
  3700K .. .. .. .. .. 62% 75.4M 0s
  3750K .. .. .. .. .. 63% 46.1M 0s
  3800K .. .. .. .. .. 64%  104M 0s
  3850K .. .. .. .. .. 65% 1.57M 0s
  3900K .. .. .. .. .. 66% 76.0M 0s
  3950K .. .. .. .. .. 67% 41.4M 0s
  4000K .. .. .. .. .. 67% 69.9M 0s
  4050K .. .. .. .. .. 68% 76.3M 0s
  4100K .. .. .. .. .. 69% 3.11M 0s
  4150K .. .. .. .. .. 70% 70.1M 0s
  4200K .. .. .. .. .. 71% 66.3M 0s
  4250K .. .. .. .. .. 72% 54.7M 0s
  4300K .. .. .. .. .. 72% 62.9M 0s
  4350K .. .. .. .. .. 73% 45.8M 0s
  4400K .. .. .. .. .. 74% 94.9M 0s
  4450K .. .. .. .. .. 75% 63.3M 0s
  4500K .. .. .. .. .. 76% 45.1M 0s
  4550K .. .. .. .. .. 77% 75.7M 0s
  4600K .. .. .. .. .. 78% 38.9M 0s
  4650K .. .. .. .. .. 78% 32.4M 0s
  4700K .. .. .. .. .. 79% 69.6M 0s
  4750K .. .. .. .. .. 80% 77.4M 0s
  4800K .. .. .. .. .. 81% 52.2M 0s
  4850K .. .. .. .. .. 82% 81.7M 0s
  4900K .. .. .. .. .. 83% 98.0M 0s
  4950K .. .. .. .. .. 83% 85.2M 0s
  5000K .. .. .. .. .. 84% 55.1M 0s
  5050K .. .. .. .. .. 85% 78.4M 0s
  5100K .. .. .. .. .. 86% 77.1M 0s
  5150K .. .. .. .. .. 87% 77.8M 0s
  5200K .. .. .. ..

[jira] [Updated] (FOP-2677) [PATCH] Text in SVG with applied filter is not rendered

2017-01-10 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/FOP-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Tošovský updated FOP-2677:
--
Attachment: (was: font-relief.svg)

> [PATCH] Text in SVG with applied filter is not rendered
> ---
>
> Key: FOP-2677
> URL: https://issues.apache.org/jira/browse/FOP-2677
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Jan Tošovský
> Attachments: FOP-2677.patch, envelope-after.pdf, envelope.fo, 
> envelope.pdf, font-relief.svg
>
>
> When attached XSL-FO with referenced SVG file is processed with FOP into PDF, 
> the text is not rendered.
> It is caused by org.apache.fop.svg.font.FOPGVTGlyphVector.draw method:
> {code:java}
> public void draw(Graphics2D graphics2d, AttributedCharacterIterator aci) {
> // NOP
> }
> {code}
> The text to render is finally passed to this method, but it does nothing.
> Originally reported as Batik Transcoder issue 
> https://issues.apache.org/jira/browse/BATIK-1133



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2677) [PATCH] Text in SVG with applied filter is not rendered

2017-01-10 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/FOP-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Tošovský updated FOP-2677:
--
Attachment: font-relief.svg
envelope-after.pdf

> [PATCH] Text in SVG with applied filter is not rendered
> ---
>
> Key: FOP-2677
> URL: https://issues.apache.org/jira/browse/FOP-2677
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Jan Tošovský
> Attachments: FOP-2677.patch, envelope-after.pdf, envelope.fo, 
> envelope.pdf, font-relief.svg
>
>
> When attached XSL-FO with referenced SVG file is processed with FOP into PDF, 
> the text is not rendered.
> It is caused by org.apache.fop.svg.font.FOPGVTGlyphVector.draw method:
> {code:java}
> public void draw(Graphics2D graphics2d, AttributedCharacterIterator aci) {
> // NOP
> }
> {code}
> The text to render is finally passed to this method, but it does nothing.
> Originally reported as Batik Transcoder issue 
> https://issues.apache.org/jira/browse/BATIK-1133



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOP-2678) [PATCH] FOPGVTGlyphVector.getGlyphOutline returns just glyph bounding box

2017-01-10 Thread JIRA 

[ 
https://issues.apache.org/jira/browse/FOP-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15816276#comment-15816276
 ] 

Jan Tošovský commented on FOP-2678:
---

For test case of attached patch see FOP-2677.

> [PATCH] FOPGVTGlyphVector.getGlyphOutline returns just glyph bounding box
> -
>
> Key: FOP-2678
> URL: https://issues.apache.org/jira/browse/FOP-2678
> Project: FOP
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jan Tošovský
> Attachments: FOP-2678.patch
>
>
> The following method returns just glyph bounding box, not a glyph shape:
> {code:java}
> public Shape getGlyphOutline(int glyphIndex) {
> Shape glyphBox = getBoundingBoxes()[glyphIndex];
> AffineTransform tr = 
> AffineTransform.getTranslateInstance(positions[glyphIndex * 2],
> positions[glyphIndex * 2 + 1]);
> AffineTransform glyphTransform = getGlyphTransform(glyphIndex);
> if (glyphTransform != null) {
> tr.concatenate(glyphTransform);
> }
> return tr.createTransformedShape(glyphBox);
> }
> {code}
> This convenient method hence cannot be used properly to address e.g.
> https://issues.apache.org/jira/browse/FOP-2677



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2678) [PATCH] FOPGVTGlyphVector.getGlyphOutline returns just glyph bounding box

2017-01-10 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/FOP-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Tošovský updated FOP-2678:
--
Summary: [PATCH] FOPGVTGlyphVector.getGlyphOutline returns just glyph 
bounding box  (was: FOPGVTGlyphVector.getGlyphOutline returns just glyph 
bounding box)

> [PATCH] FOPGVTGlyphVector.getGlyphOutline returns just glyph bounding box
> -
>
> Key: FOP-2678
> URL: https://issues.apache.org/jira/browse/FOP-2678
> Project: FOP
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jan Tošovský
> Attachments: FOP-2678.patch
>
>
> The following method returns just glyph bounding box, not a glyph shape:
> {code:java}
> public Shape getGlyphOutline(int glyphIndex) {
> Shape glyphBox = getBoundingBoxes()[glyphIndex];
> AffineTransform tr = 
> AffineTransform.getTranslateInstance(positions[glyphIndex * 2],
> positions[glyphIndex * 2 + 1]);
> AffineTransform glyphTransform = getGlyphTransform(glyphIndex);
> if (glyphTransform != null) {
> tr.concatenate(glyphTransform);
> }
> return tr.createTransformedShape(glyphBox);
> }
> {code}
> This convenient method hence cannot be used properly to address e.g.
> https://issues.apache.org/jira/browse/FOP-2677



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2678) FOPGVTGlyphVector.getGlyphOutline returns just glyph bounding box

2017-01-10 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/FOP-2678?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Tošovský updated FOP-2678:
--
Attachment: FOP-2678.patch

> FOPGVTGlyphVector.getGlyphOutline returns just glyph bounding box
> -
>
> Key: FOP-2678
> URL: https://issues.apache.org/jira/browse/FOP-2678
> Project: FOP
>  Issue Type: Bug
>Affects Versions: trunk
>Reporter: Jan Tošovský
> Attachments: FOP-2678.patch
>
>
> The following method returns just glyph bounding box, not a glyph shape:
> {code:java}
> public Shape getGlyphOutline(int glyphIndex) {
> Shape glyphBox = getBoundingBoxes()[glyphIndex];
> AffineTransform tr = 
> AffineTransform.getTranslateInstance(positions[glyphIndex * 2],
> positions[glyphIndex * 2 + 1]);
> AffineTransform glyphTransform = getGlyphTransform(glyphIndex);
> if (glyphTransform != null) {
> tr.concatenate(glyphTransform);
> }
> return tr.createTransformedShape(glyphBox);
> }
> {code}
> This convenient method hence cannot be used properly to address e.g.
> https://issues.apache.org/jira/browse/FOP-2677



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2677) [PATCH] Text in SVG with applied filter is not rendered

2017-01-10 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/FOP-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Tošovský updated FOP-2677:
--
Summary: [PATCH] Text in SVG with applied filter is not rendered  (was: 
Text in SVG with applied filter is not rendered)

> [PATCH] Text in SVG with applied filter is not rendered
> ---
>
> Key: FOP-2677
> URL: https://issues.apache.org/jira/browse/FOP-2677
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Jan Tošovský
> Attachments: FOP-2677.patch, envelope.fo, envelope.pdf, 
> font-relief.svg
>
>
> When attached XSL-FO with referenced SVG file is processed with FOP into PDF, 
> the text is not rendered.
> It is caused by org.apache.fop.svg.font.FOPGVTGlyphVector.draw method:
> {code:java}
> public void draw(Graphics2D graphics2d, AttributedCharacterIterator aci) {
> // NOP
> }
> {code}
> The text to render is finally passed to this method, but it does nothing.
> Originally reported as Batik Transcoder issue 
> https://issues.apache.org/jira/browse/BATIK-1133



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2677) Text in SVG with applied filter is not rendered

2017-01-10 Thread JIRA 

 [ 
https://issues.apache.org/jira/browse/FOP-2677?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jan Tošovský updated FOP-2677:
--
Attachment: FOP-2677.patch

Rendering outlines with proper fill and stroke style. However, outlines are 
rendered as bounding boxes. This is addressed in a separate issue.

> Text in SVG with applied filter is not rendered
> ---
>
> Key: FOP-2677
> URL: https://issues.apache.org/jira/browse/FOP-2677
> Project: FOP
>  Issue Type: Bug
>Affects Versions: 2.1
>Reporter: Jan Tošovský
> Attachments: FOP-2677.patch, envelope.fo, envelope.pdf, 
> font-relief.svg
>
>
> When attached XSL-FO with referenced SVG file is processed with FOP into PDF, 
> the text is not rendered.
> It is caused by org.apache.fop.svg.font.FOPGVTGlyphVector.draw method:
> {code:java}
> public void draw(Graphics2D graphics2d, AttributedCharacterIterator aci) {
> // NOP
> }
> {code}
> The text to render is finally passed to this method, but it does nothing.
> Originally reported as Batik Transcoder issue 
> https://issues.apache.org/jira/browse/BATIK-1133



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOP-2324) [PATCH] Character not found in AFP font but no warning is issued

2017-01-10 Thread simon steiner (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOP-2324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814886#comment-15814886
 ] 

simon steiner commented on FOP-2324:


Can we see fop.xconf?

> [PATCH] Character not found in AFP font but no warning is issued
> 
>
> Key: FOP-2324
> URL: https://issues.apache.org/jira/browse/FOP-2324
> Project: FOP
>  Issue Type: Improvement
>  Components: font/unqualified
>Affects Versions: trunk
>Reporter: Seifeddine Dridi
>Priority: Minor
> Fix For: trunk
>
> Attachments: patch.diff
>
>
> I noticed that the AFP font system never files a warning whenever a character 
> was not found in the font, unlike font systems for other output formats where 
> a warning is always displayed whenever FOP detects a possible error.
> Apparently, this is mainly happening because there is no defined mapping 
> between Unicode values and font code points for AFP, as can be seen in 
> CharacterSet.mapChar(). That's why I propose to change it to:
> public char mapChar(char c) {
> //TODO This is not strictly correct but we'll let it be for the moment
> if (this.encoder.canEncode(c)) {
> return c;
> }
> return 0;
> }
> So we can check later in AbstractOutlineFont.mapChar() whenever a character 
> was found or not and display a warning if necessary.
> Any thoughts?
> Thanks



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FOP-2362) [PATCH] Using Saxon to intermediate format throws NullPointerException

2017-01-10 Thread simon steiner (JIRA) 

[ 
https://issues.apache.org/jira/browse/FOP-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15814614#comment-15814614
 ] 

simon steiner commented on FOP-2362:


http://svn.apache.org/viewvc?view=revision=1778105

> [PATCH] Using Saxon to intermediate format throws NullPointerException
> --
>
> Key: FOP-2362
> URL: https://issues.apache.org/jira/browse/FOP-2362
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 1.1
> Environment: Apple OSX 10.9.2 / Java version 1.7.0_11
>Reporter: Hauke Haastert
>Assignee: simon steiner
> Attachments: extensions.diff, simple.xsl, test.fo
>
>
> When rendering an XSL-FO file that contains an AFP-Extension to the 
> intermediate format while using Saxon as XSLT transformer, a 
> NullPointerException is thrown.
> Steps to reproduce:
> 1. Download and unpack the FOP 1.1 binary release.
> 2. Change into the root directory "fop-1.1" of the release
> 3. Download Saxon HE from 
> http://repo1.maven.org/maven2/net/sf/saxon/Saxon-HE/9.4/Saxon-HE-9.4.jar and 
> copy the file to the lib directory of the FOP 1.1 release
> 4. Edit the file fop that is located in the root directory of the release and 
> add the following JVM parameter to the java_exec_args:
> 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
> The line should now look like:
> java_exec_args="-Djava.awt.headless=true 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl"
> 5. Download the attached files test.fo and simple.xsl and run the following 
> fop command:
> fop -fo test.fo -out application/X-fop-intermediate-format test.if.xml
> Actual Results:
> Application throws NullPointerException:
> java.lang.NullPointerException
> at 
> net.sf.saxon.event.ReceivingContentHandler.getNodeName(ReceivingContentHandler.java:391)
> at 
> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:316)
> at 
> org.apache.fop.util.DelegatingContentHandler.startElement(DelegatingContentHandler.java:185)
> at 
> org.apache.fop.render.afp.extensions.AFPPageSetup.toSAX(AFPPageSetup.java:125)
> at 
> org.apache.fop.render.intermediate.IFSerializer.handleExtensionObject(IFSerializer.java:680)
> Expected Results:
> Application should render IF from FO
> Additional Information:
> In the toSAX method of the class 
> org.apache.fop.render.afp.extensions.AFPPageSetup the method addAttribute of 
> the class org.xml.sax.helpers.AttributesImpl is called with null as first 
> argument. Due to the APIDOC of the class org.xml.sax.helpers.AttributesImpl 
> the first argument must either be the namespace or an empty string, but not 
> null:
> uri - The Namespace URI, or the empty string if none is available or 
> Namespace processing is not being performed.
> When changing the parameter value to an empty string, no NullPointerException 
> is thrown anymore. The same problem exists in other classes in the package 
> org.apache.fop.render.afp.extensions, so I added a diff file for the complete 
> package (extensions.diff).
> The exception is not thrown when using Xalan as XSL transformer. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FOP-2362) [PATCH] Using Saxon to intermediate format throws NullPointerException

2017-01-10 Thread simon steiner (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FOP-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner resolved FOP-2362.

Resolution: Fixed

> [PATCH] Using Saxon to intermediate format throws NullPointerException
> --
>
> Key: FOP-2362
> URL: https://issues.apache.org/jira/browse/FOP-2362
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 1.1
> Environment: Apple OSX 10.9.2 / Java version 1.7.0_11
>Reporter: Hauke Haastert
>Assignee: simon steiner
> Attachments: extensions.diff, simple.xsl, test.fo
>
>
> When rendering an XSL-FO file that contains an AFP-Extension to the 
> intermediate format while using Saxon as XSLT transformer, a 
> NullPointerException is thrown.
> Steps to reproduce:
> 1. Download and unpack the FOP 1.1 binary release.
> 2. Change into the root directory "fop-1.1" of the release
> 3. Download Saxon HE from 
> http://repo1.maven.org/maven2/net/sf/saxon/Saxon-HE/9.4/Saxon-HE-9.4.jar and 
> copy the file to the lib directory of the FOP 1.1 release
> 4. Edit the file fop that is located in the root directory of the release and 
> add the following JVM parameter to the java_exec_args:
> 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
> The line should now look like:
> java_exec_args="-Djava.awt.headless=true 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl"
> 5. Download the attached files test.fo and simple.xsl and run the following 
> fop command:
> fop -fo test.fo -out application/X-fop-intermediate-format test.if.xml
> Actual Results:
> Application throws NullPointerException:
> java.lang.NullPointerException
> at 
> net.sf.saxon.event.ReceivingContentHandler.getNodeName(ReceivingContentHandler.java:391)
> at 
> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:316)
> at 
> org.apache.fop.util.DelegatingContentHandler.startElement(DelegatingContentHandler.java:185)
> at 
> org.apache.fop.render.afp.extensions.AFPPageSetup.toSAX(AFPPageSetup.java:125)
> at 
> org.apache.fop.render.intermediate.IFSerializer.handleExtensionObject(IFSerializer.java:680)
> Expected Results:
> Application should render IF from FO
> Additional Information:
> In the toSAX method of the class 
> org.apache.fop.render.afp.extensions.AFPPageSetup the method addAttribute of 
> the class org.xml.sax.helpers.AttributesImpl is called with null as first 
> argument. Due to the APIDOC of the class org.xml.sax.helpers.AttributesImpl 
> the first argument must either be the namespace or an empty string, but not 
> null:
> uri - The Namespace URI, or the empty string if none is available or 
> Namespace processing is not being performed.
> When changing the parameter value to an empty string, no NullPointerException 
> is thrown anymore. The same problem exists in other classes in the package 
> org.apache.fop.render.afp.extensions, so I added a diff file for the complete 
> package (extensions.diff).
> The exception is not thrown when using Xalan as XSL transformer. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FOP-2362) [PATCH] Using Saxon to intermediate format throws NullPointerException

2017-01-10 Thread simon steiner (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FOP-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner updated FOP-2362:
---
Summary: [PATCH] Using Saxon to intermediate format throws 
NullPointerException  (was: [PATCH] Rendering AFP extension to intermediate 
format throws NullPointerException)

> [PATCH] Using Saxon to intermediate format throws NullPointerException
> --
>
> Key: FOP-2362
> URL: https://issues.apache.org/jira/browse/FOP-2362
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 1.1
> Environment: Apple OSX 10.9.2 / Java version 1.7.0_11
>Reporter: Hauke Haastert
>Assignee: simon steiner
> Attachments: extensions.diff, simple.xsl, test.fo
>
>
> When rendering an XSL-FO file that contains an AFP-Extension to the 
> intermediate format while using Saxon as XSLT transformer, a 
> NullPointerException is thrown.
> Steps to reproduce:
> 1. Download and unpack the FOP 1.1 binary release.
> 2. Change into the root directory "fop-1.1" of the release
> 3. Download Saxon HE from 
> http://repo1.maven.org/maven2/net/sf/saxon/Saxon-HE/9.4/Saxon-HE-9.4.jar and 
> copy the file to the lib directory of the FOP 1.1 release
> 4. Edit the file fop that is located in the root directory of the release and 
> add the following JVM parameter to the java_exec_args:
> 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
> The line should now look like:
> java_exec_args="-Djava.awt.headless=true 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl"
> 5. Download the attached files test.fo and simple.xsl and run the following 
> fop command:
> fop -fo test.fo -out application/X-fop-intermediate-format test.if.xml
> Actual Results:
> Application throws NullPointerException:
> java.lang.NullPointerException
> at 
> net.sf.saxon.event.ReceivingContentHandler.getNodeName(ReceivingContentHandler.java:391)
> at 
> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:316)
> at 
> org.apache.fop.util.DelegatingContentHandler.startElement(DelegatingContentHandler.java:185)
> at 
> org.apache.fop.render.afp.extensions.AFPPageSetup.toSAX(AFPPageSetup.java:125)
> at 
> org.apache.fop.render.intermediate.IFSerializer.handleExtensionObject(IFSerializer.java:680)
> Expected Results:
> Application should render IF from FO
> Additional Information:
> In the toSAX method of the class 
> org.apache.fop.render.afp.extensions.AFPPageSetup the method addAttribute of 
> the class org.xml.sax.helpers.AttributesImpl is called with null as first 
> argument. Due to the APIDOC of the class org.xml.sax.helpers.AttributesImpl 
> the first argument must either be the namespace or an empty string, but not 
> null:
> uri - The Namespace URI, or the empty string if none is available or 
> Namespace processing is not being performed.
> When changing the parameter value to an empty string, no NullPointerException 
> is thrown anymore. The same problem exists in other classes in the package 
> org.apache.fop.render.afp.extensions, so I added a diff file for the complete 
> package (extensions.diff).
> The exception is not thrown when using Xalan as XSL transformer. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (FOP-2362) [PATCH] Rendering AFP extension to intermediate format throws NullPointerException

2017-01-10 Thread simon steiner (JIRA) 

 [ 
https://issues.apache.org/jira/browse/FOP-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

simon steiner reassigned FOP-2362:
--

Assignee: simon steiner

> [PATCH] Rendering AFP extension to intermediate format throws 
> NullPointerException
> --
>
> Key: FOP-2362
> URL: https://issues.apache.org/jira/browse/FOP-2362
> Project: FOP
>  Issue Type: Bug
>  Components: unqualified
>Affects Versions: 1.1
> Environment: Apple OSX 10.9.2 / Java version 1.7.0_11
>Reporter: Hauke Haastert
>Assignee: simon steiner
> Attachments: extensions.diff, simple.xsl, test.fo
>
>
> When rendering an XSL-FO file that contains an AFP-Extension to the 
> intermediate format while using Saxon as XSLT transformer, a 
> NullPointerException is thrown.
> Steps to reproduce:
> 1. Download and unpack the FOP 1.1 binary release.
> 2. Change into the root directory "fop-1.1" of the release
> 3. Download Saxon HE from 
> http://repo1.maven.org/maven2/net/sf/saxon/Saxon-HE/9.4/Saxon-HE-9.4.jar and 
> copy the file to the lib directory of the FOP 1.1 release
> 4. Edit the file fop that is located in the root directory of the release and 
> add the following JVM parameter to the java_exec_args:
> 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl
> The line should now look like:
> java_exec_args="-Djava.awt.headless=true 
> -Djavax.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl"
> 5. Download the attached files test.fo and simple.xsl and run the following 
> fop command:
> fop -fo test.fo -out application/X-fop-intermediate-format test.if.xml
> Actual Results:
> Application throws NullPointerException:
> java.lang.NullPointerException
> at 
> net.sf.saxon.event.ReceivingContentHandler.getNodeName(ReceivingContentHandler.java:391)
> at 
> net.sf.saxon.event.ReceivingContentHandler.startElement(ReceivingContentHandler.java:316)
> at 
> org.apache.fop.util.DelegatingContentHandler.startElement(DelegatingContentHandler.java:185)
> at 
> org.apache.fop.render.afp.extensions.AFPPageSetup.toSAX(AFPPageSetup.java:125)
> at 
> org.apache.fop.render.intermediate.IFSerializer.handleExtensionObject(IFSerializer.java:680)
> Expected Results:
> Application should render IF from FO
> Additional Information:
> In the toSAX method of the class 
> org.apache.fop.render.afp.extensions.AFPPageSetup the method addAttribute of 
> the class org.xml.sax.helpers.AttributesImpl is called with null as first 
> argument. Due to the APIDOC of the class org.xml.sax.helpers.AttributesImpl 
> the first argument must either be the namespace or an empty string, but not 
> null:
> uri - The Namespace URI, or the empty string if none is available or 
> Namespace processing is not being performed.
> When changing the parameter value to an empty string, no NullPointerException 
> is thrown anymore. The same problem exists in other classes in the package 
> org.apache.fop.render.afp.extensions, so I added a diff file for the complete 
> package (extensions.diff).
> The exception is not thrown when using Xalan as XSL transformer. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)