The main problem is that it's not going to the next page; it's
displaying the original page.  The next page doesn't need the bean, but
it would be nice to go to the next page.  If I copy-paste the
<h:commandLink> to be outside the dataTable, then I get to the next page
fine.  But, for some reason, if I click on the same <h:commandLink> from
within the dataTable, the original page gets displayed again with an
empty bean.  Usually, this would be a sign that there was an error
encountered (although the component tree should then be restored).  But
I can't see that an error was encountered, since <h:messages> doesn't
show anything.  Also, I'm sure that the outcome was spelled right, since
copying and pasting it outside of the dataTable works.

Oh, well, just wondering if someone else had a similar experience.  I'll
have to trap the MyFaces conversation in the debugger to see what it
thinks is going on....

- Brendan

-----Original Message-----
From: Mike Kienenberger [mailto:[EMAIL PROTECTED] 
Sent: Monday, August 15, 2005 2:29 PM
To: MyFaces Discussion
Subject: Re: Using <h:commandLink> inside <t:column>


Does it work if you change your backing bean to session scope?
If so, the solution might be to t:saveState your backing bean.

Not sure why the link isn't working, but if it depends on the
datatable data, that could be related to the above.

On 8/15/05, CONNER, BRENDAN (SBCSI) <[EMAIL PROTECTED]> wrote:
> Has anyone had any trouble using <h:commandLink> inside <t:column>?
I'm
> still trying to figure out what's going wrong, but the symptom is that
> the page with the table gets displayed fine, and then, when I click on
> the link, the same page gets displayed, but this time with all the
data
> missing.  (The backing bean has request scope.)   The new page
indicated
> by the link doesn't get displayed.  The same link works fine outside
of
> <t:column>.  It just seems to fail inside the <t:column>.  (BTW,
> <t:column> is specified inside <t:dataTable>.)
> 
> - Brendan
>

Reply via email to