Re: [jsr-314-open-mirror] [jsr-314-open] [ADMIN] Expert Community meeting 20100714 13:00 EDT: UIData

Thanks Alexander - find below a slightly extended version of your document (sorry to put it in a mail, but I couldn´t edit the Google Doc). I didn´t find an issue for "supporting AJAX updates of single rows" - can you add this, so it doesn´t get lost? best regards, Martin JSF 2.1 iteration components. 1. Create root class ( interface ? ) for all iteration components: UIRepeat, UIDataTable,and, if possible, UISelectItems, and all similar third-party components ( lists, trees, grids, menus ) that iterate over its children. There would be class hierarchy similar to the ADF/trinidad: UICollection -- UIRepeater -- UIDataTable -- HtmlDataTable -- UIHierarchy .... (https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=322) 2. In addition to saving state of EditableValueHolder between iterations, save similar information for components that use internal fields during requests. That includes UIData/UIRepeat itself ( data model instance and saved states from children ), UIForm ( 'submitted' property ), and any other components that can require per-row states. Possible implementations: Lets components do it on its own by implementing IterationStateHolder interface with two methods saveIterationState/restoreIterationState. Using partial state to store per-row values in the same way as it is done between requests - this should be implemented in any case, partial state saving in a table right now does not work.( https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=545, https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=153, 3. Support AJAX updates for a single row in iteration components, and allow AJAX requests from inside the table to find the table (getClientId wrongly returns the id of the row inside the client-id, see https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=865, duplicate of https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=738) 4. Move column rendering from dataTable to column component itself, to create custom column components that performs some logic ( for example, iterate over children components to create columns 'on the fly' like t:columns component does ) or customize column look and fell. DataTable should relay on "Column" interface instead of UIColumn component. ( related issues : https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=217, https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=225, https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=627 , https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=756) 5. Enhance data model to support Collection interface ( https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=479 , https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=713, https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=751), or use arbitrary key instead of simple row number, so developers would use database Primary Key's for JPA-based models. Custom keys also required by hierarchal components. Additional wish for UIData (not sure we want this?): https://javaserverfaces-spec-public.dev.java.net/issues/show_bug.cgi?id=249 Facets should accept arbitrary attributes... best regards, Martin On Tue, Jul 13, 2010 at 10:28 PM, Alexander Smirnov <asmirnov(a)exadel.com&gt; wrote: -- http://www.irian.at Your JSF powerhouse - JSF Consulting, Development and Courses in English and German Professional Support for Apache MyFaces