[JAVASERVERFACES_SPEC_PUBLIC-989] Programmatic manipulation of list items Created: 25/Apr/11  Updated: 01/Aug/14

Status: Open
Project: javaserverfaces-spec-public
Component/s: Components/Renderers
Affects Version/s: 1.1, 1.2, 2.0, 2.1
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Ed Burns Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Status Whiteboard:

size_large importance_large


 Description   

JB> 3) programmatically manipulation of an item in a displayed list -
JB> The <ui:repeat/> is ok, but ASP.NET ups the ante once again by
JB> letting you raise a method on the backing class to easily manipulate
JB> the child components for the current row

JB> Example tag

JB> <asp:Repeater ID="rptEvents" runat="server"
JB> OnItemDataBound="handleRepeaterRow" >

JB> .... child components here

JB> </ asp:Repeater>

JB> Corresponding method on the backing class

JB> protected void handleRepeaterRow(object sender,
JB> System.Web.UI.WebControls.RepeaterItemEventArgs e)

JB> this is REALLY powerful as it provides an excellent way to solve
JB> issue #2 plus a whole lot more



 Comments   
Comment by lamine_ba [ 25/Apr/11 ]

One solution of this problem could be to attach to the <ui:repeat> component an event or an action to be executed?
Now the missing piece is the intention of the developer? What he want to do in the server side? what does he need?

1) The current index
2) The current Object
3) the current UI representation of the current object

Comment by lamine_ba [ 27/Apr/11 ]

JB> Yes to all of the above. As proposed in the JIRA item I think the ability to call a method on the <ui:repeat /> would be optimal. Forgive my pseudo code but maybe something like this:

public void handleRepeatItem(Object currentObjectFromCollection, UIComponent currentContainerHoldingChildComponents)

MLB> Thus you can programmaticaly create an UI representation for your object and attach this representation to its UI container (Builder Pattern). From a programmer perspective, I can only appreciate this solution which is really scalable at the condition you don't keep the UI reference (UIComponent currentContainerHoldingChildComponents). Once we have this feature, I bet that any programmer will say " Oh! I love it so much. I have now the freedom to do whatever I want" and I bet that any web designer will say " Oh! I hate it so much. I can't program and I can't help. Who can save a wretch like me? "

Comment by Ed Burns [ 01/Aug/14 ]

Set priority to baseline ahead of JSF 2.3 triage. Priorities will be assigned accurately after this exercise.

Comment by Manfred Riem [ 01/Aug/14 ]

Setting priority to Minor

Generated at Wed Jul 29 20:42:14 UTC 2015 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.