Re: NPE while generating multi language pdf with FOP 1.1

2015-07-24 Thread Glenn Adams
No. But you are welcome to patch and build a local copy yourself. On Thu, Jul 23, 2015 at 1:39 PM, jeya venkatesh M wrote: > Hello, > > We are migrating from FOP 1.0 to 1.1. I get NPE while generating a multi > language PDF. It usually worked in 1.0. > > I verified that this

NPE while generating multi language pdf with FOP 1.1

2015-07-24 Thread jeya venkatesh M
Hello, We are migrating from FOP 1.0 to 1.1. I get NPE while generating a multi language PDF. It usually worked in 1.0. I verified that this is associated with issue FOP 2415 is fixed as part 2.0. As of now, we are not in position to upgrade to 2.0. Is there any option to get it fixed in patch

Re: NPE from GraphicsUtil.getAlphaRaster

2014-06-20 Thread Pascal Sancho
I'm speaking about GraphicsUtil.getAlphaRaster(), of course. 2014-06-20 10:36 GMT+02:00 Pascal Sancho : > Note: I'm not sure getAlphaRaster() may return null. If true, your > patch should be against xmlgraphics rather than fop. -- pascal -

Re: NPE from GraphicsUtil.getAlphaRaster

2014-06-20 Thread Pascal Sancho
Hi, You should provide a test case (short xsl-fo + image causing NPE). Did you test against FOP 1.1 or FOP trunk? For submitting a Patch, please open a dedicated issue in Jira (see [1] for further details). Note: I'm not sure getAlphaRaster() may return null. If true, your patch shou

NPE from GraphicsUtil.getAlphaRaster

2014-06-19 Thread Shane Witbeck
Hi, We use FOP 1.0 for converting documents to PDF. In certain cases when the document contains an image that returns null from GraphicsUtil.getAlphaRaster, this results in a NPE shown below: 2014-06-19 10:08:12,932 [http-nio-8080-exec-4] [1:admin:REGULAR] ERROR

Re: NPE when rendering fo:block-container inside fo:inline

2008-09-09 Thread Vincent Hennebert
Hi Frank, Frank Worsley wrote: > Hello, > > I am using the Antenna House XSL stylesheets to convert XHTML to > XML-FO. This works very well in most cases. However, I have come > across a problem where a fo:block-container inside a fo:inline will > cause an NPE. > >

NPE when rendering fo:block-container inside fo:inline

2008-09-05 Thread Frank Worsley
Hello, I am using the Antenna House XSL stylesheets to convert XHTML to XML-FO. This works very well in most cases. However, I have come across a problem where a fo:block-container inside a fo:inline will cause an NPE. An example FO file that exhibits this problem is attached. The stack trace is

Re: Fop-0.95: NPE when having an empty -element with hyphenation turned on

2008-08-21 Thread Marco
Original-Nachricht > Datum: Thu, 21 Aug 2008 18:50:38 +0200 > Von: Andreas Delmelle <[EMAIL PROTECTED]> > An: fop-users@xmlgraphics.apache.org > Betreff: Re: Fop-0.95: NPE when having an empty -element with > hyphenation turned on > On Aug 21, 200

Re: Fop-0.95: NPE when having an empty -element with hyphenation turned on

2008-08-21 Thread Andreas Delmelle
On Aug 21, 2008, at 15:09, Marco wrote: Hi all, I get a NullPointerException (see end of message) when transforming the following file with fop-0.95. (fop-0.94 can handle this). It only happens when hyphenation is set to true and if the element does not contain any text (I came across th

Fop-0.95: NPE when having an empty -element with hyphenation turned on

2008-08-21 Thread Marco
Hi all, I get a NullPointerException (see end of message) when transforming the following file with fop-0.95. (fop-0.94 can handle this). http://www.w3.org/1999/XSL/Format";>

RE: Forward references in marker element throws NPE

2008-07-04 Thread Browning, Jamie
build myself. Jamie Browning theFrame Programme Phone: +44 (0)20 7015 0981 E-mail: [EMAIL PROTECTED] -Original Message- From: Andreas Delmelle [mailto:[EMAIL PROTECTED] Sent: 03 July 2008 19:26 To: fop-users@xmlgraphics.apache.org Subject: Re: Forward references in marker element throws NPE

Re: Forward references in marker element throws NPE

2008-07-03 Thread Andreas Delmelle
On Jul 2, 2008, at 19:54, Andreas Delmelle wrote: On Jul 2, 2008, at 11:30, Browning, Jamie wrote: Hi Jamie If there is any way in which I can positively influence the decision to include this patch then I would like to do so. You're playing with fire here... |8-> In the meantime, I have

Re: Forward references in marker element throws NPE

2008-07-02 Thread Andreas Delmelle
On Jul 2, 2008, at 11:30, Browning, Jamie wrote: Hi Jamie If there is any way in which I can positively influence the decision to include this patch then I would like to do so. You're playing with fire here... |8-> In the meantime, I have already applied the changes. It's literally only

RE: Forward references in marker element throws NPE

2008-07-02 Thread Browning, Jamie
0981 E-mail: [EMAIL PROTECTED] -Original Message- From: Andreas Delmelle [mailto:[EMAIL PROTECTED] Sent: 01 July 2008 19:45 To: fop-users@xmlgraphics.apache.org Subject: Re: Forward references in marker element throws NPE On Jul 1, 2008, at 16:02, Browning, Jamie wrote: Hi Jamie, > M

Re: Forward references in marker element throws NPE

2008-07-01 Thread Andreas Delmelle
On Jul 1, 2008, at 16:02, Browning, Jamie wrote: Hi Jamie, Many thanks for your prompt responses Andreas/Chris Andreas I have seen your commit on Bugzilla. One question I have though is will this fix be merged into the 0.95 release candidate? I guess I could commit it to the release branc

RE: Forward references in marker element throws NPE

2008-07-01 Thread Browning, Jamie
- From: Andreas Delmelle [mailto:[EMAIL PROTECTED] Sent: 26 June 2008 21:15 To: fop-users@xmlgraphics.apache.org Subject: Re: Forward references in marker element throws NPE On Jun 26, 2008, at 21:33, Andreas Delmelle wrote: >> >> On Jun 26, 2008, at 17:06, Browning, Jamie w

RE: Forward references in marker element throws NPE

2008-06-27 Thread Browning, Jamie
> A NPE is bad indeed. Can you open a bug in bugzilla and attach some > sample FO that demonstrates the problem? https://issues.apache.org/bugzilla/show_bug.cgi?id=45295 > Despite of the NPE, markers are not supposed to be forward referencable. > The fo:retrieve-marker is suppose

Re: Forward references in marker element throws NPE

2008-06-27 Thread Chris Bowditch
Browning, Jamie wrote: All Am I right in assuming that forward references in marker elements no longer work in FOP 0.9x? My assumption is based on the fact that the marker examples included in the binary dist for both 0.94 and 0.95beta are throwing a NullPointerException. A NPE is bad

Re: Forward references in marker element throws NPE

2008-06-26 Thread Andreas Delmelle
On Jun 26, 2008, at 21:33, Andreas Delmelle wrote: On Jun 26, 2008, at 17:06, Browning, Jamie wrote: My assumption is based on the fact that the marker examples included in the binary dist for both 0.94 and 0.95beta are throwing a NullPointerException. I'll see what I can find based on th

Re: Forward references in marker element throws NPE

2008-06-26 Thread Andreas Delmelle
On Jun 26, 2008, at 21:20, Andreas Delmelle wrote: Errm... Sorry, one of those days... Just noticed: On Jun 26, 2008, at 17:06, Browning, Jamie wrote: My assumption is based on the fact that the marker examples included in the binary dist for both 0.94 and 0.95beta are throwing a NullPointe

Re: Forward references in marker element throws NPE

2008-06-26 Thread Andreas Delmelle
On Jun 26, 2008, at 17:06, Browning, Jamie wrote: Am I right in assuming that forward references in marker elements no longer work in FOP 0.9x? Not sure if I understand your question correctly... Do you mean something like: id="{$forward-reference}" /> ? I assume so, as a fo:retrieve-mar

Forward references in marker element throws NPE

2008-06-26 Thread Browning, Jamie
All Am I right in assuming that forward references in marker elements no longer work in FOP 0.9x? My assumption is based on the fact that the marker examples included in the binary dist for both 0.94 and 0.95beta are throwing a NullPointerException. For example: I need to different footers to app

Re: FOP on 10g AS NPE

2008-01-30 Thread Jeremias Maerki
at org.apache.fop.fo.FObjMixed.(FObjMixed.java:72) > > I have attached the .fo file. has anyone seen this before? > > Thanks > James > http://www.nabble.com/file/p15177236/.docgen56959.fo .docgen56959.fo > > -- > View this message in context: > http:

FOP on 10g AS NPE

2008-01-30 Thread yodakoda
.java:72) I have attached the .fo file. has anyone seen this before? Thanks James http://www.nabble.com/file/p15177236/.docgen56959.fo .docgen56959.fo -- View this message in context: http://www.nabble.com/FOP-on-10g-AS-NPE-tp15177236p15177236.html Sent from the FOP - Users mailing lis

RE: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-12-03 Thread Peter
> In any case if you generate PDF you should specify measurements > in mm, pt or in. Oops...sorry for the extra noise, thanks, Peter. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-30 Thread J.Pietschmann
Peter wrote: Fop now says SEVERE: file:///c:/temp/lala.fo:9:42: No conversion defined 40; property:'height' This is unrelated to the barcode/font issue, it means FOP can't convert the value into something it understands. I think this is a bug in FOP (measurements without a unit should be inter

RE: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-30 Thread Peter
I found the TrueType versions of the 2 barcode fonts I was using and those work just fine. Peter > -Original Message- > From: Peter [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 30, 2006 8:42 AM > To: 'fop-users@xmlgraphics.apache.org' > Subject: RE: NPE

RE: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-29 Thread Peter
iginal Message- > From: Jeremias Maerki [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 30, 2006 7:41 AM > To: fop-users@xmlgraphics.apache.org > Subject: Re: NPE IN SingleByteFont.hasChar when using IDAutomationC39S > font > > The problem is the "UnknownEncoding

Re: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-29 Thread Jeremias Maerki
d/relevant. > > Attached the metrics file. > > All guidance where to look is appreciated, > > Thanks, > > Peter > > > -Original Message- > > From: J.Pietschmann [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, November 29, 2006 11:32 PM &

RE: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-29 Thread Peter
TECTED] > Sent: Wednesday, November 29, 2006 11:32 PM > To: fop-users@xmlgraphics.apache.org > Subject: Re: NPE IN SingleByteFont.hasChar when using IDAutomationC39S > font > > Peter wrote: > > I am trying to use a Barcode font (IDAutomationC39S) and I am getting an >

Re: NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-29 Thread J.Pietschmann
Peter wrote: I am trying to use a Barcode font (IDAutomationC39S) and I am getting an NPE with the following trace listed lower. Barcode fonts are tricky, because barcode glyphs are not separate unicode glyphs. It seems that the encoding for your font is unknown. Try to generate the font

NPE IN SingleByteFont.hasChar when using IDAutomationC39S font

2006-11-29 Thread Peter
Gentlepeople, I am trying to use a Barcode font (IDAutomationC39S) and I am getting an NPE with the following trace listed lower. Before I dive into the debugger and try to find out what is going on, has anyone any idea whether a barcode font is supposed to work and/or what could be wrong. The

Re: NPE

2006-03-09 Thread Andreas L Delmelle
On Mar 9, 2006, at 00:17, Glen Mazza wrote: Hi Glen, [EMAIL PROTECTED] wrote: Whitespace verifies as #PCDATA if #PCDATA is allowed at a particular point. If #PCDATA is NOT allowed at a particular point, the whitespace is ignored for the purposes of verifying. So we are currently handling

Re: NPE

2006-03-08 Thread Glen Mazza
[EMAIL PROTECTED] wrote: Whitespace verifies as #PCDATA if #PCDATA is allowed at a particular point. If #PCDATA is NOT allowed at a particular point, the whitespace is ignored for the purposes of verifying. So we are currently handling it correct for XML whitespace. Now, we could catch t

Re: NPE

2006-03-08 Thread a_l . delmelle
>- Oorspronkelijk bericht - >Van: Glen Mazza [mailto:[EMAIL PROTECTED] > >Andreas L Delmelle wrote: > >> In the latter case, however: >> >> >> >> ... >> >> >> >> Note that the i-f-o now contains two text nodes (= #PCDATA): >> ' ' and ' ' >> > >I think they call that "insignifica

Re: NPE

2006-03-07 Thread Glen Mazza
Andreas L Delmelle wrote: In the latter case, however: ... Note that the i-f-o now contains two text nodes (= #PCDATA): ' ' and ' ' I think they call that "insignificant white space", and that would not be counted as PCDATA. Partly explained here, but not definitive either

Re: NPE

2006-03-07 Thread Andreas L Delmelle
On Mar 7, 2006, at 02:38, Glen Mazza wrote: Hi Glen, Andreas L Delmelle wrote: On Mar 6, 2006, at 10:05, Florent Georges wrote: The fo:instream-foreign-object flow object has a child from a non-XSL namespace. The permitted structure of this child is that defined for that namespa

Re: NPE

2006-03-06 Thread Glen Mazza
Andreas L Delmelle wrote: On Mar 6, 2006, at 10:05, Florent Georges wrote: Andreas L Delmelle wrote: On Mar 6, 2006, at 01:25, Florent Georges wrote: Well, AFAICT, it's not really empty from a SAX parser's point of view. It does contain a text-node, but this is completely ignored by FOP.

Re: NPE

2006-03-06 Thread Andreas L Delmelle
On Mar 6, 2006, at 10:05, Florent Georges wrote: Andreas L Delmelle wrote: On Mar 6, 2006, at 01:25, Florent Georges wrote: Well, AFAICT, it's not really empty from a SAX parser's point of view. It does contain a text-node, but this is completely ignored by FOP. The SAX characters() events

Re: NPE

2006-03-06 Thread Florent Georges
Andreas L Delmelle wrote: > On Mar 6, 2006, at 01:25, Florent Georges wrote: > > Andreas L Delmelle wrote: > >> The problem is an empty fo:instream-foreign-object. > > Thanks for the solution (mmh, this file passed my > > validator, I'll have to check that). > Well, AFAICT, it's not really e

Re: NPE

2006-03-05 Thread Andreas L Delmelle
On Mar 6, 2006, at 01:25, Florent Georges wrote: Andreas L Delmelle wrote: The problem is an empty fo:instream-foreign-object. Thanks for the solution (mmh, this file passed my validator, I'll have to check that). Well, AFAICT, it's not really empty from a SAX parser's point of view. I

Re: NPE

2006-03-05 Thread Florent Georges
Andreas L Delmelle wrote: > The problem is an empty fo:instream-foreign-object. Thanks for the solution (mmh, this file passed my validator, I'll have to check that). Regards, --drkm __

Re: NPE

2006-03-05 Thread Andreas L Delmelle
ign-object. Just patched FOP Trunk so now a ValidationException is thrown instead of an NPE. Cheers, Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

NPE

2006-03-05 Thread Florent Georges
Hi While running some tests, I found an NullPointerException with 0.91: ~> fop contract.fo contract.pdf Exception java.lang.NullPointerException Attached the contract.fo file. I'm sorry I don't have time to locate more precisely the error to reduce the size of this file (I hav

Re: NPE in Fop Task

2006-02-15 Thread Jeremias Maerki
06 11:47:36 Eike Stepper wrote: > >> Jeremias Maerki schrieb: > >>> Actually, I wanted the FOP version, too. After searching through the > >>> various FOP versions with the line number from the stack trace I found > >>> that you're talking about 0

Re: NPE in Fop Task

2006-02-15 Thread Eike Stepper
th 0.91beta You're using the "fop" task inside a "macrodef". I believe the NPE happens due to the Project instance not being set on the task which the Task.log() method needs. Maybe that's because the "fop" task is inside a "macrodef", but I can&

Re: NPE in Fop Task

2006-02-15 Thread Jeremias Maerki
arching through the > > various FOP versions with the line number from the stack trace I found > > that you're talking about 0.20.5. > > Sorry, you're right this is Fop 0.20.5, although the same thing happens with > 0.91beta > > > > You're using

Re: NPE in Fop Task

2006-02-15 Thread Eike Stepper
0.91beta You're using the "fop" task inside a "macrodef". I believe the NPE happens due to the Project instance not being set on the task which the Task.log() method needs. Maybe that's because the "fop" task is inside a "macrodef", but I can't te

Re: NPE in Fop Task

2006-02-15 Thread Jeremias Maerki
Actually, I wanted the FOP version, too. After searching through the various FOP versions with the line number from the stack trace I found that you're talking about 0.20.5. You're using the "fop" task inside a "macrodef". I believe the NPE happens due to the Project

Re: NPE in Fop Task

2006-02-15 Thread Eike Stepper
I use JDK1.5.0_06 and this is the trace (the switches are very useful!): Apache Ant version 1.6.5 compiled on June 2 2005 Apache Ant version 1.6.5 compiled on June 2 2005 Buildfile: C:\ws\genfw\com.sympedia.docs\scripts\build.xml +Datatype genfw com.sympedia.genfw.ant.GenfwTask +Datatype copy.

Re: NPE in Fop Task

2006-02-15 Thread Jeremias Maerki
Always state the FOP and JDK version you're using. You can run Ant using the "-d" or "-v" parameters and then you should get stack traces. On 15.02.2006 07:16:55 Eike Stepper wrote: > Hi, > > I get a NullPointerException when calling Fop from my Ant script: > > > >

NPE in Fop Task

2006-02-14 Thread Eike Stepper
Hi, I get a NullPointerException when calling Fop from my Ant script: