I suppose you are paging with <t:dataScroller>. Then try with the next datascroller's attribute:
renderFacetsIfSinglePage="" I think you have to put it to "false"... ----- Mensaje original ---- De: Torsten Krah <[EMAIL PROTECTED]> Para: [EMAIL PROTECTED] CC: MyFaces Discussion <[email protected]> Enviado: lunes, 28 de mayo, 2007 19:19:50 Asunto: Re: DataScroller - Rendering/Pagination problem when rendered attribute is set to a conditional EL expression This rendered stuff has even more problems: Using: rendered="#{not empty @managed-bean-name.users}" at my t:dataTable, does result in breaking all actions, the table might emit (deleting rows, editing some). Using facestrace and message tag, no errors - lifecycle does complete all 6 phases - but nothing happens - my bean methods aren't invoked. Navigation actions neither. No exceptions - all looks good, but nothing is done. If i remove the rendered attribute of the table - stuff works again. Did i miss something about the rendered attribute? Torsten Am Montag, den 28.05.2007, 18:44 +0200 schrieb Torsten Krah: > I want to render the paginator only, if the actual datasize is greater > than the actual row size. > > > Setting > > rendered="[EMAIL PROTECTED] gt @managed-bean-name.rows}" > > does reflect that and works, but if i got a list size of 2 and changing > the rows to 1 - paginator shows 2 pages. > But you can't change the page - you are bound to page 1. > > Deleting the rendered EL expression - paginator works again, but is > there all the time. > > Should be a bug, shouldn't it? > > Torsten ____________________________________________________________________________________ ¡Descubre una nueva forma de obtener respuestas a tus preguntas! Entra en Yahoo! Respuestas. http://es.answers.yahoo.com/info/welcome
