RE: NullPointerException

[Matt Dong <ma...@camilion.com>]

We tried the latest fop.jar(0.95) which generated from FOP trunk, but still got the null point exception.

Please see attached FO producing the error.

Thanks,
Matt Dong


-----Original Message-----
From: Andreas Delmelle [mailto:andreas.delmelle@telenet.be] 
Sent: Tuesday, December 23, 2008 5:18 PM
To: fop-users@xmlgraphics.apache.org
Subject: Re: NullPointerException

On 23 Dec 2008, at 21:57, Matt Dong wrote:

Hi

> We got the following null pointer exception when using  
> transformer.transform(Source xmlSource, Result outputTarget). In the  
> xmlSource, We pass the corect FO directory.
> Now We use the fop.jar (0.95), but change back to fop.jar(0.93)  
> works fine.
>
> Is there anyone know this issue?
<snip />
>
> java.lang.NullPointerException
> 2008-12-23 14:55:16,711 INFO  [STDOUT]               at  
> org 
> .apache 
> .fop 
> .fo 
> .flow 
> .table.ConditionalBorder.integrateSegment(ConditionalBorder.java:168)
> 2008-12-23 14:55:16,711 INFO  [STDOUT]               at  
> org.apache.fop.fo.flow.table.TableFObj.createBorder(TableFObj.java: 
> 262)


I don't immediately remember having run into this one. I did notice  
that the corresponding code has been slightly modified in FOP trunk.  
Could be the issue is already fixed there.

Any chance you could test it with trunk to confirm? If not, can you  
provide the FO producing the error, so we can check here?

Thanks

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org

Re: NullPointerException

[Andreas Delmelle <an...@telenet.be>]

On 06 Jan 2009, at 20:38, Matt Dong wrote:

Hi

> We tried the latest fop.jar(0.95) which generated from FOP trunk,  
> but still got the null point exception.
>
> Please see attached FO producing the error.

Thanks for the example. This indeed seems to be a bug, or a slight  
oversight. FOP does already support border-collapse="collapse", but  
not "collapse-with-precedence".

If you need an immediate workaround, make sure you replace all  
occurrences of "collapse-with-precence" with simply "collapse". After  
doing that, no more error over here.

It may take some playing with the border specs on the various table  
elements to get the borders entirely right, though. If I judge  
correctly, the result is not 100% presentable (?)


HTH!

Andreas

---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org