Yeah, I don't think we really gain anything by not specifying columns for a dataList-like component, so I don't see a problem with requiring them. The advantages of maintaining a single t:dataList are obvious.
On 1/17/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > I see what you mean now. I think you have a good idea, but there are a few > attributes, like @layout for dataList, that are not currently there for the > t:dataTable component. Also, I think it may be technically difficult because > UIData looks for columns and facets for processUpdates and processDecodes - > and, of course, neither of these are children for dataList. > > I think someone (maybe Simon) brought this up a long time ago. Whoever did > it, their concern was that UIData was "hopping over" UIColumns to carry out > processing - instead of telling each column to do it. > > Dennis Byrne > > >-----Original Message----- > >From: Mike Kienenberger [mailto:[EMAIL PROTECTED] > >Sent: Tuesday, January 17, 2006 02:28 PM > >To: 'MyFaces Discussion' > >Subject: Re: I need help in dataList. > > > >Exactly. We need dataList's renderer ported over to dataTable, and > >then we can just dump the dataList component. > > > >On 1/17/06, Dennis Byrne <[EMAIL PROTECTED]> wrote: > >> >If you can't make it render like you want, then create your own > >> >renderer for t:dataTable, and submit it as a replacement for dataList > >> > >> I agree that t:dataTable is probably a better alternative. The problems > >> with dataList actually have to do with the UIComponent rather than it's > >> renderer. In current SVN, it will decode properly (events from children > >> are registered) but it does not update the model. > >> > >> Dennis Byrne > >> > >> > >> > > > > >
