Issue Details (XML | Word | Printable)

Key: JAVASERVERFACES_SPEC_PUBLIC-628
Type: Bug Bug
Status: Open Open
Priority: Major Major
Assignee: Unassigned
Reporter: driscoll
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
javaserverfaces-spec-public

"always render" javascript API

Created: 14/Sep/09 06:02 AM   Updated: 05/Jan/14 01:13 PM
Component/s: Ajax/JavaScript
Affects Version/s: 2.0
Fix Version/s: 2.3

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All


Issuezilla Id: 628
Status Whiteboard:

size_small importance_large

Tags:
Participants: driscoll, Ed Burns, Hanspeter Duennenberger and rogerk


 Description  « Hide

RichFaces has the notion of autoupdate - a list of "always render" id's, that
are rendered for every ajax request.

A quick, naive implementation could be as simple as:

void jsf.ajax.addAlwaysRender(String id)

and then every jsf.ajax.request would have the "id" appended to the render list.

This would be trivial to implement.

The use case for this is actually a special case for component authors - while a
page author can manually add id's to the render list, component authors can't.



Ed Burns added a comment - 24/Sep/09 09:13 AM

Move to unscheduled target milestone


Ed Burns added a comment - 24/Nov/09 07:40 AM

Prepare to delete api subcomponent


rogerk added a comment - 18/Jun/10 03:33 AM

triage


Ed Burns added a comment - 22/Jun/10 09:02 PM

edburns


Ed Burns added a comment - 22/Jun/10 10:35 PM

2.1


Ed Burns added a comment - 24/Jun/10 02:41 PM

GlassFish 3.1 M6 at the latest.


rogerk added a comment - 29/Jun/10 10:25 AM

Correct Subcomponent


rogerk added a comment - 01/Jul/10 12:00 PM

re-target


rogerk added a comment - 26/Aug/10 03:51 AM

triage


rogerk added a comment - 16/Nov/10 12:37 PM

triage


Hanspeter Duennenberger added a comment - 05/Jan/14 01:13 PM

Hi,

my 2 cents to this idea:

Why would that always id's have to be part of the jsf ajax api? Ids of components to always update could be managed server side only. Beside, sometimes it is also handy to execute a component with every request (aka always).

We implemented it in csJSF as a separate tag that can be placed on a page or template and is used like this:

<x:always execute="space separated id list" render="space separated id list" />

The mixin of the always to execute/render ids was done in a PartialViewContextWrapper - if this becomes JSF standard then mixin would be in PartialViewContext itself.

Best regards
Hanspeter