myfaces-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "CONNER, BRENDAN \(SBCSI\)" <bc1...@sbc.com>
Subject RE: DataTable Problem
Date Thu, 27 Oct 2005 15:24:32 GMT
We fixed the problem we were having by saving the state of the table's backing bean using <t:saveState>.
 Now, the button within the table fires fine.

- Brendan

-----Original Message-----
From: Mathias Brökelmann [mailto:mbroekelmann@googlemail.com] 
Sent: Thursday, October 27, 2005 2:51 AM
To: MyFaces Discussion
Subject: Re: DataTable Problem


We have quite a lot of such issues. Maybe we should add a check if the
number of rows in the decode phase don´t match with the row number
while rendering.

2005/10/26, CONNER, BRENDAN (SBCSI) <bc1378@sbc.com>:
> Oh, I understand now.  Sorry for being so dense!
>
> Thanks to both of you!
>
> - Brendan
>
> -----Original Message-----
> From: Mike Kienenberger [mailto:mkienenb@gmail.com]
> Sent: Wednesday, October 26, 2005 11:29 AM
> To: MyFaces Discussion
> Subject: Re: DataTable Problem
>
>
> What Mathias is saying is that you have to maintain the model during
> the Restore View phase for the next page.    Without a model, your
> command link is effectively set to rendered=false, and no action event
> will be generated.   I've never tested to see if it matters what model
> is available on the next page, but I'd expect it'd have to be the same
> model in order for you to determine which row was clicked, if that is
> important to you.
>
> On 10/26/05, CONNER, BRENDAN (SBCSI) <bc1378@sbc.com> wrote:
> > #{maintainSkillBean.skillList} returns at least one row, because that provides the
link that we click.  The problem is, when we click the link, the next page does not get displayed.
> >
> > - Brendan
> >
> > -----Original Message-----
> > From: Mathias Brökelmann [mailto:mbroekelmann@googlemail.com]
> > Sent: Wednesday, October 26, 2005 3:05 AM
> > To: MyFaces Discussion
> > Subject: Re: DataTable Problem
> >
> >
> > The value for #{maintainSkillBean.skillList} must not return null or
> > an empty list during the decode phase. Place a debug-breakpoint into
> > the getter method to see when it is called. You can also use
> > t:datatable and preserveDataModel="true".
> >
> > 2005/10/26, CONNER, BRENDAN (SBCSI) <bc1378@sbc.com>:
> > > We're experiencing a problem using a commandLink (or commandButton)
> > > inside a dataTable.  We're hoping that it's just something we're doing
> > > wrong.
> > >
> > > If we copy the commandLink outside the dataTable (just as a test), and
> > > then click on the commandLink outside the dataTable, then control goes
> > > to the desired page.
> > >
> > > However, if we click on the commandLink that is inside the table, the
> > > same page gets displayed (with an empty table).
> > >
> > > Here is the JSP code:
> > >
> > > <t:commandLink action="displayHome" title="Skill Id"
> > > styleClass="commandLinkHomePage">
> > >         <h:outputText value="test" styleClass="link"/>
> > > </t:commandLink>
> > >
> > > <t:dataTable value="#{maintainSkillBean.skillList}" var="element"
> > > headerClass="reportHeader" columnClasses="reportDetailLeft"
> > > cellpadding="2" cellspacing="2">
> > >         <t:column>
> > >                 <f:facet name="header">
> > >                         <h:outputText value="Skill Id"/>
> > >                 </f:facet>
> > >                 <t:commandLink action="displayHome" title="Skill Id"
> > > styleClass="commandLinkHomePage" >
> > >                         <h:outputText value="#{element.skillId}"
> > > styleClass="link"/>
> > >                 </t:commandLink>
> > >         </t:column>
> > > </t:dataTable>
> > >
> > > Any clues about why clicking the first commandLink would correctly bring
> > > us to the home page, whereas clicking the second commandLink would just
> > > redisplay the current page?  We have <t:messages> up top, and no error
> > > messages are getting displayed.
> > >
> > > - Brendan
> > >
> > > P.S. We tried this with both 1.1.1RC2 and 1.1.1RC3, and we're getting
> > > the same result.  We also tried using both <t:dataTable> and
> > > <h:dataTable>, but still no luck.
> > >
> >
> >
> > --
> > Mathias
> >
>


--
Mathias

Mime
View raw message