Re: I need help in dataList.
Yes..dataTable is working fine with me.Thanks a lot for replies
Re: I need help in dataList.
Good idea. Make dataTable support dataList's layouts, especially "simple", and remove dataList. For the "simple" layout, dataTable does not have a workaround. We need that ! Also please add another attribute: newspaper, and remove newspaper component. consolidate and make life easier :)Mike Kienenberger <[EMAIL PROTECTED]> wrote: Exactly. We need dataList's renderer ported over to dataTable, andthen 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>>> Yahoo! Photos Got holiday prints? See all the ways to get quality prints in your hands ASAP.
Re: I need help in dataList.
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 > >> > >> > >> > > > > >
Re: I need help in dataList.
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 >> >> >> >
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 > > >
Re: I need help in dataList.
>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
Re: I need help in dataList.
Marco, UIData components (like t:dataList/h:dataTable/t:dataTable/t:newspaperTable/t:columns) use a Flyweight pattern. http://www.exciton.cs.rice.edu/JavaResources/DesignPatterns/FlyweightPattern.htm What this means is that one component is used multiple times to encode/render and decode/parse your inputs. Each instance of this is row-state data. dataList seems to do the least well with handling the handling of all of these row-state data pieces. Probably dataList should be dumped, and replaced with a custom t:dataTable renderer. I'd recommend trying to switch over to using t:dataTable. Once you do that, you can try using preserveRowStates/preserveDataModel/previousRowDataVar to make your situation work. 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 :) It should just be a matter of deleting all of the generated table tags for the simple layout. On 1/17/06, Marco <[EMAIL PROTECTED]> wrote: > Any suggestions please... > > All i need to do is to update the model from the generated UI components > from the dataList. > > Thanks a lot >
Re: I need help in dataList.
Any suggestions please...All i need to do is to update the model from the generated UI components from the dataList.Thanks a lot
I need help in dataList.
Hi Everybody;I have a case that the user will enter a number and then I'll generate HTML TextAreas it's count is equal to the number he entered.And i did that with the dataList.But i need if he updated these textAreas i can get the updated values.
Here is sample code styleClass="standardList" var="myObject" value="#{
bean.list}" rowCountVar="rowCount" rowIndexVar="rowIndex">
I thought "#{myObject.comments}" will update my bean "comments attribute", but after form submission the entered values in the textareas disappeared and the bean was not updated with the new values.
So, What should i do ?Thanks
