[JAVASERVERFACES_SPEC_PUBLIC-678] Add new client event type - between complete and success Created: 02/Dec/09  Updated: 12/Aug/14

Status: Open
Project: javaserverfaces-spec-public
Component/s: Ajax/JavaScript
Affects Version/s: 2.0
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: driscoll Assignee: Unassigned
Resolution: Unresolved Votes: 8
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Attachments: Text File jsf-spec.patch    
Issuezilla Id: 678
Status Whiteboard:

size_medium important_large


 Description   

There is a desire to have a new client event - coming between complete, and
success. While success is the event thrown when all the incoming commands are
successfully executed, it would be useful to have an event after each incoming
command is executed.

There would of course need to be additional information in the data payload of
this event: id effected, presumably, as well as the name of command executed
(update, eval, etc.) Maybe more? TBD.



 Comments   
Comment by ganeshpuri [ 21/Jan/10 ]

corrected target

Comment by Ed Burns [ 22/Jun/10 ]

rogerk

Comment by rogerk [ 23/Jun/10 ]

triage

Comment by rogerk [ 30/Jun/10 ]
      • Issue 734 has been marked as a duplicate of this issue. ***
Comment by rogerk [ 30/Jun/10 ]

I'm adding verbage from other spec issue that will benefit from this:

Some kind of notification for AJAX-updated DOM elements is necessary to let
components being updated by AJAX to free memory. Details of the problem are
described in this thread at RichFaces forum:
http://community.jboss.org/thread/5742?tstart=0 .

Setting target (schedule) as well.

Comment by werpu [ 26/Aug/10 ]

Having sunk tremendous time recently into fixing client side ie gc issues on
MyFaces I can feel the pain of the component authors myself here.

From my personal experience we need two events here one for startProcessing...
with the command details, so that any pre cleanup work can be performed (saving
old dom nodes for further cleaning up etc...)

and a postProcessing event which then allows the cleanup. So I would add a
startCommand and endCommand event here with further details about the command
being passed down.

Comment by rogerk [ 27/Aug/10 ]

For now re-target for 2.2.
If time permits may revisit for 2.1.

Comment by nick_belaevski [ 26/Oct/10 ]

Created an attachment (id=317)
Proposed patch

Comment by rogerk [ 16/Nov/10 ]

triage

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.

Generated at Mon Aug 29 08:47:23 UTC 2016 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.