Ok.  I'm now seeing this problem as well (don't know how I missed it before).

I think Michael is correct in that this is caused by the combination
of newspaperTable and dataScroller.

I've been able to reproduce it by having a dataTable with one item,
but a rows value of 10.

The newspaperRows are computed to be 10 (this is a table with no
newpaperColumns), and this is how we get to setRowIndex(1) instead of
stopping at setRowIndex(0).

In the original t:dataTable code, we did this, where rowIndex was
iterating from first to last.

          uiData.setRowIndex(rowIndex);

          //scrolled past the last row
          if (!uiData.isRowAvailable())
              break;


Michael's suggestion was to use this:

           last = first + rows;
+           if (last > uiData.getRowCount())
+           {
+                   last=uiData.getRowCount();
+                }

I think this is probably the correct fix for the problem.
It will definitely fix non-newspaper tables.    It won't affect
newspaper tables without scrollers.    I've tried following it through
with newspaper tables with scrollers and it looks like that should
work as well.

I don't have a current checkout of the myfaces code, so if someone
else could apply Michael's patch, I'd appreciate it.


On 7/20/06, Michael Heinen <[EMAIL PROTECTED]> wrote:
I tried also to fix this issue.

The index of the last row is set to uiData.getRowCount() if it was
bigger before. Empty rows without cells are not rendered anymore.
I didn't test this with the newspaper stuff.

Hope this helps.

Regards,
Michael

-----Original Message-----
From: Martin Marinschek [mailto:[EMAIL PROTECTED]
Sent: Montag, 17. Juli 2006 17:58
To: MyFaces Discussion; Mike Kienenberger
Subject: Re: HtmlTableRendererBase Error: Row is not available. Rowindex
= 0

I committed a quickfix to this, where I do not return, but break if a
row is not available.

This is not the final solution, though.

Mike, you committed the original patch for merging newspaperdatatable
and datatable - anything you can say about this?

regards,

Martin

On 7/17/06, iSquareOne LLC <[EMAIL PROTECTED]> wrote:
>
> Thanks, Michael!
> I think for now, we have to just disable the output in log4j.xml. I
hope the
> development team can resolve this issue soon, because it's very
annoying.
>
> - Shawn
>
>
> Michael Heinen <[EMAIL PROTECTED]> wrote:
>
>
>
> This is already a JIRA issue (TOMAHAWK-467).
> http://issues.apache.org/jira/browse/TOMAHAWK-467
> It is not fixed yet.
>
>
>  ________________________________
>
> From: iSquareOne LLC [mailto:[EMAIL PROTECTED]
> Sent: Samstag, 15. Juli 2006 05:35
> To: Users Myfaces
> Subject: HtmlTableRendererBase Error: Row is not available. Rowindex =
0
>
>
> Hey, all,
>
> We built MyFaces 1.1.4 using source code as of 7/12. Everything works
fine
> but in the log, it always says:
>
>
>
> 2006-07-14 16:49:17,062 ERROR
>
[org.apache.myfaces.shared_tomahawk.renderkit.html.HtmlTableRendererBase
]
> Row is not available. Rowindex = 0
>
> We use a dataTable on the page.
>
>
>
> Anyone know why this error is thrown? It did not affect the function,
but I
> would like to get rid of this error if possible.
>
>
>
> Thanks!
>
>
>
> - Shawn
>  __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
>  __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com


--

http://www.irian.at

Your JSF powerhouse -
JSF Consulting, Development and
Courses in English and German

Professional Support for Apache MyFaces





Reply via email to