I added my comments below for GET for paging and sorting -----Original Message----- From: Srinivas Surapaneni [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 11, 2006 10:18 PM To: 'Beehive Users' Subject: RE: composite components using tag files
I will try the datagrid again with the <netui:form> tags and see how the url's are generated for paging and sorting Thank You -----Original Message----- From: Eddie O'Neil [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 11, 2006 10:11 PM To: Beehive Users Subject: Re: composite components using tag files Comments in line... On 4/11/06, Srinivas Surapaneni <[EMAIL PROTECTED]> wrote: > If I am using a editable grid, I want to use < netui:textbox > dataSource="container.item.xxxxxx - where xxxxx I want to use from the list > of columns that got passed into the tag as attribute [eko] Apologies -- I think I misunderstood before. When you say "the list of columns", you mean the data in the data set being rendered in the data grid. :) Yes, this should be possible -- just wrap the data grid itself or a specific row in a <netui:form> tag. I looked, and we don't seem to have a sample of this, which is unfortunate. I've added a JIRA issue: http://issues.apache.org/jira/browse/BEEHIVE-1098 to track adding one. > > One more question on the datagrid > > All the datagrid urls are plain url's , not form posts > When we want to use the dataGrid for editable grids, we need to post it. > Basically, for all the sorting and paging we have to post the form. Is there > any plan to provide this feature? [eko] Not sure I understand this -- could you describe your use case in a little more detail? Today, the data grid does paging and sorting as HTTP GETs so that the links are bookmarkable and don't require form POSTs. Currently, I don't have any plans to change this behavior. For editable data grids, you should be able to POST a form for a specific row or for the entire data grid, but that's separate from the links for sorting, filtering, and paging, which is state that can be stored on the server and "re-attached" when an edit is finished. [Srinivas] I understand the links are bookmarkable. But when we provide a editable grid, the user should be able to do anything ( changes to the values, paging, sorting etc) and should be able to keep all his changes during all the operations ). If you use GET for paging and sorting, you will lose all the changes Myfaces Tomhawk, ADF and lot of third party components use POST for all the operations of a editable grid Again, I'll try to put together an example of this, but it's going to take me a couple of weeks to complete because of some other committments in the interim. > > > Thank You > > > -----Original Message----- > From: Eddie O'Neil [mailto:[EMAIL PROTECTED] > Sent: Tuesday, April 11, 2006 9:36 PM > To: Beehive Users > Subject: Re: composite components using tag files > > Comments in line... > > > On 4/11/06, Srinivas Surapaneni <[EMAIL PROTECTED]> wrote: > > I am trying to build composite components from netui tags > > > > [eko] It should be possible to build composite components from the > NetUI tags. The only limitation that I'm aware of is that some NetUI > JSP tags can't be split across a JSP and a .tag file because they use > the method "findAncestorWithClass" which requires some JSP tags to be > in a single JSP tag hierarchy. > > > > > > > Ex: There is no dual list component, calendar component in beehive > > [eko] True -- feel free to contribute one! :) > > > > > I am trying to use the new JSP tag file mechanism to create a tag file > which > > contains all the components required for the dual list > > > > > > > > But I need to pass the select options for List 1 , List 2 and 2 > datasources > > to the tag as attributes > > > > > > [eko] The NetUI "dataSource" attribute is a little special as it's > used to round-trip data into a page, to the browser, and back to the > server on a POST. Usually, you'd only reference the "actionForm" > implicit object from a "dataSource". For repeating tags like the data > grid, you might reference many other things. The "netui-samples" web > application provides some good examples of this, and documentation on > the nuances of the "dataSource" attribute are described here: > > http://beehive.apache.org/docs/1.0.1/netui/databinding.html > > To pass the options to a select box, you'd use the "optionsDataSource" > tag for the choices and use "dataSource" as the place data is stored > when a JSP POSTs. The netui-samples/ webapp in the distribution has > examples of this. > > > > > > > > > But the datasource does not take runtime expressions. Is there any way to > > use runtime expressions for netui components like textBox, select, > checkbox > > etc > > > > [eko] On the dataSource attribute, this is (unfortunately) not > possible because of limitations in the JSP 2.0 Expression Language, > though the rest of the attributes should be runtime expressionable. > > > > > > > Other thing we are tryinh to create is reusable datagrid > > > > > > > > We want to create a list of column names in the pageflow scope and in the > > reusable datagrid > > > > > > > > we want to use container.item.xxxxxxxx - where xxxxx comes from the > column > > list. > > > > > > > > Is there any easy way to do this? > > > > > > [eko] I don't know why this shouldn't work, but you'll need to use the > appropriate JSTL tag to render all of the <netui-data:headerCell>s > from inside of the <netui-data:header> tag. But, I've not tried it -- > if you run into trouble with it, let me know. > > > > > -- > > No virus found in this outgoing message. > > Checked by AVG Free Edition. > > Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 > > > > > > > > -- > No virus found in this incoming message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 > > > -- > No virus found in this outgoing message. > Checked by AVG Free Edition. > Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 > > > -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.385 / Virus Database: 268.4.0/305 - Release Date: 4/8/2006
