Re: Large table cell crashes fop92

2006-05-19 Thread Arturo Perez
Jeremias Maerki dev at jeremias-maerki.ch writes:

 
 
 
  The marker thing I put in for 
  0.92 but I think I get the same crash under 0.20.5.
 
 Really? 0.20.5's layout engine is working completely differently. I
 can't imagine you get the same error.
 


Not exactly the same but it looks similar enough.

java.lang.ArrayIndexOutOfBoundsException: -2
at org.apache.fop.fo.flow.TableRow$CellArray.getNextFreeCell(TableRow.ja
va:134)
at org.apache.fop.fo.flow.TableRow.initCellArray(TableRow.java:512)
at org.apache.fop.fo.flow.TableRow.layout(TableRow.java:275)
at org.apache.fop.fo.flow.AbstractTableBody.layout(AbstractTableBody.jav
a:236)
at org.apache.fop.fo.flow.Table.layout(Table.java:302)
at org.apache.fop.fo.flow.AbstractFlow.layout(AbstractFlow.java:154)

So the cause is an emtpy table cell?  Or is it a cell that wraps and the
wrapping doesn't create anything?


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Large table cell crashes fop92

2006-05-18 Thread Jeremias Maerki
Please send an FO-file (no XSLT!) that demonstrates the problem. My own
tests show no problems with table-cells longer than the available page
height.

On 17.05.2006 20:51:11 Arturo Perez wrote:
 Hi all,
 
 I have a very large table-cell that crashes fop-0.92beta.  The cell in 
 question
 seems to be 11.75 inches tall while the page is only allowed to be 8in in the
 page-sequence.  I found this out by playing with the page-sequence/region
 definitions.  Any suggestions on how to work around it?
 
 Here's the beginning of the stack trace.
 
 java.lang.NullPointerException
 at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:167)
 at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:114)
 at org.apache.fop.cli.Main.startFOP(Main.java:159)
 at org.apache.fop.cli.Main.main(Main.java:190)
 
 -
 
 java.lang.NullPointerException
 at 
 org.apache.fop.layoutmgr.AbstractLayoutManager.isFirst(AbstractLayout
 Manager.java:349)
 at 
 org.apache.fop.layoutmgr.AreaAdditionUtil.addAreas(AreaAdditionUtil.j
 ava:90)
 at 
 org.apache.fop.layoutmgr.table.TableCellLayoutManager.addAreas(TableC
 ellLayoutManager.java:418)
 at 
 org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.a
 ddAreasForCell(TableContentLayoutManager.java:973)
 at 
 org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.a
 ddAreasAndFlushRow(TableContentLayoutManager.java:925)
 at 
 org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.h
 andleTableContentPosition(TableContentLayoutManager.java:782)
 at 
 org.apache.fop.layoutmgr.table.TableContentLayoutManager.iterateAndPa
 intPositions(TableContentLayoutManager.java:740)


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Large table cell crashes fop92

2006-05-18 Thread Jeremias Maerki
I was able to commit a change that avoids the NullPointerException.
However, there's a problem remaining that I cannot fix quickly. Your
markers may not be treated correctly or in other words: They won't be
added for the cases a table-cell produces an empty area as on page 9 in
your example. retrieve-marker might return the wrong values. Due to the
obfuscation of your document I cannot easily see if it affects you.

Note to fop-devs: If there are no Position instances returned by the
Iterator in AreaAdditionUtil.addAreas(), there's currently no way to
determine the first/last conditions for the addMarker calls. We have a
similar problem for page-number-citation-last where it's difficult to
know when the last area of an element is painted and the element is
essentially finished. We will need to find a way around that. Don't know
how, yet. I've added a test case that shows the problem.

http://svn.apache.org/viewvc?rev=407614view=rev

On 18.05.2006 17:53:00 Arturo Perez wrote:
 Here's a zipped obfuscated fo file.  I did try removing the 
 keep-together=always on the table rows but that resulted in a slightly 
 different crash.
 
 Thanks so much for helping me with this.
 
  dir.zip 
 
 -arturo
 



Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Large table cell crashes fop92

2006-05-18 Thread Perez
In article [EMAIL PROTECTED],
 Jeremias Maerki [EMAIL PROTECTED] wrote:

 I was able to commit a change that avoids the NullPointerException.
 However, there's a problem remaining that I cannot fix quickly. Your
 markers may not be treated correctly or in other words: They won't be
 added for the cases a table-cell produces an empty area as on page 9 in
 your example. retrieve-marker might return the wrong values. Due to the
 obfuscation of your document I cannot easily see if it affects you.
 
 http://svn.apache.org/viewvc?rev=407614view=rev
 Jeremias Maerki

Is there anything I can do differently?  The marker thing I put in for 
0.92 but I think I get the same crash under 0.20.5.  Does that mean that 
the fox: extension has the same problem?

thanks again,
-arturo


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: Large table cell crashes fop92

2006-05-18 Thread Jeremias Maerki

On 19.05.2006 01:09:32 Perez wrote:
 In article [EMAIL PROTECTED],
  Jeremias Maerki [EMAIL PROTECTED] wrote:
 
  I was able to commit a change that avoids the NullPointerException.
  However, there's a problem remaining that I cannot fix quickly. Your
  markers may not be treated correctly or in other words: They won't be
  added for the cases a table-cell produces an empty area as on page 9 in
  your example. retrieve-marker might return the wrong values. Due to the
  obfuscation of your document I cannot easily see if it affects you.
  
  http://svn.apache.org/viewvc?rev=407614view=rev
  Jeremias Maerki
 
 Is there anything I can do differently?

It depends on the requirements for your document. Since I don't know
them I can't tell. You'll have to figure out yourself whether this
limitation is a problem for you.

 The marker thing I put in for 
 0.92 but I think I get the same crash under 0.20.5.

Really? 0.20.5's layout engine is working completely differently. I
can't imagine you get the same error.

  Does that mean that 
 the fox: extension has the same problem?

That's something else. The fox: extension have all not been
reimplemented in FOP 0.92beta. fox:outline has been replaced by the XSL
1.1 fo:bookmarks.


Jeremias Maerki


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Large table cell crashes fop92

2006-05-17 Thread Arturo Perez
Hi all,

I have a very large table-cell that crashes fop-0.92beta.  The cell in question
seems to be 11.75 inches tall while the page is only allowed to be 8in in the
page-sequence.  I found this out by playing with the page-sequence/region
definitions.  Any suggestions on how to work around it?

Here's the beginning of the stack trace.

java.lang.NullPointerException
at org.apache.fop.cli.InputHandler.transformTo(InputHandler.java:167)
at org.apache.fop.cli.InputHandler.renderTo(InputHandler.java:114)
at org.apache.fop.cli.Main.startFOP(Main.java:159)
at org.apache.fop.cli.Main.main(Main.java:190)

-

java.lang.NullPointerException
at org.apache.fop.layoutmgr.AbstractLayoutManager.isFirst(AbstractLayout
Manager.java:349)
at org.apache.fop.layoutmgr.AreaAdditionUtil.addAreas(AreaAdditionUtil.j
ava:90)
at org.apache.fop.layoutmgr.table.TableCellLayoutManager.addAreas(TableC
ellLayoutManager.java:418)
at org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.a
ddAreasForCell(TableContentLayoutManager.java:973)
at org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.a
ddAreasAndFlushRow(TableContentLayoutManager.java:925)
at org.apache.fop.layoutmgr.table.TableContentLayoutManager$RowPainter.h
andleTableContentPosition(TableContentLayoutManager.java:782)
at org.apache.fop.layoutmgr.table.TableContentLayoutManager.iterateAndPa
intPositions(TableContentLayoutManager.java:740)


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]