Thanks For your reply. The reason I have kept the bean in session scope and using binding is, I am using the same table on different screens and I want to maintain the selections and other things performed on the table across the screens.
Scott O'Bryan wrote: > > Your binding should never be session scoped. > > On Mon 20 Feb 2012 10:52:32 PM MST, Nitin Khekare wrote: >> >> Hi >> >> I am getting ArrayIndexOutOfBoundsException on JBoss 6.1 for trinidad >> table >> component. >> >> The scenario is like, I am using same table component on two different >> pages >> with the backing bean in session scope and the table has binding >> attribute >> in xhtml page. The first page is getting rendered fine, but when second >> page >> starts rendering the exception comes. And the reason for exception is the >> column count is getting increased, and it increases in multiple of actual >> column number. If I remover binding for the jsf page, then everything >> works >> fine. >> >> I am using JBoss 6.1.0, JSF 1.2 and trinidad components. >> The same thing is working fine in JBoss 4.2.3. >> >> Can anybody help me in this? >> >> Thanks > > -- View this message in context: http://old.nabble.com/Getting-ArrayIndexOutOfBoundsException-on-JBoss-6.1-for-trinidad-table-component-tp33361827p33368591.html Sent from the MyFaces - Users mailing list archive at Nabble.com.
