Please submit a new JIRA ticket for this
On Mon, Jun 23, 2008 at 9:58 AM, Mathias Walter <[EMAIL PROTECTED]> wrote: > Hi, > > there is one more bug. If you editable fields in the treetable and a > validator (i.ee required) set, then the treetable fails to submit. > Just hiding the root element is not enough. You must initialise all fields > of the root node to valid values. > > The treetable component should not access any fields except the children > field, of the root element if it's hidden. > > I'll open an issue. > > -- > Kind regards, > Mathias > >> -----Original Message----- >> From: Andrew Robinson [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, June 18, 2008 5:15 PM >> To: MyFaces Discussion >> Subject: Re: [Trinidad] Displaying more than one root element >> in tr:treeTable >> >> >> I tried to look into adding multiple roots, but the refactoring was >> way too much work. I ended up adding the hide root node functionality >> instead. With that said, there is an open bug on the treeTable with >> the root node hidden that breaks command link events that I have yet >> to look into. Just wanted to make sure you consider that. >> >> On Wed, Jun 18, 2008 at 2:57 AM, Michael Meierhoff >> <[EMAIL PROTECTED]> wrote: >> > Hi Bart, >> > >> > no it is not possible to have more than one root element in >> a a treeTable. >> > What you can do is, add one root element and hide this. >> This is what have >> > done. >> > >> > Best regards Michael >> > >> > [EMAIL PROTECTED] schrieb: >> > >> > Hi all, >> > >> > We're using a tr:treeTable in our project and it is >> required that more than >> > one item of the topmost level is shown. In other words, we >> have to get rid >> > of the "show 1-1 from 23" pull down box; we don't want >> pagination fot this >> > application. We tried the rowsByDepth parameter of the >> treeTable, but it >> > seems to have influence on all levels except the top level. >> Is there a way >> > to display more than one item of the top level? Or is it >> simply impossible? >> > (We're thinking of adding a single top element to our >> model, but that's not >> > a really elegant solution in my opinion.) >> > >> > Best regards, >> > Bart Kummel > >
