[JAVASERVERFACES_SPEC_PUBLIC-613] Support standard AJAX server-side method invocation Created: 15/Aug/09  Updated: 30/May/16  Resolved: 30/May/16

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

Type: Improvement Priority: Critical
Reporter: lincolnbaxter Assignee: balusc
Resolution: Fixed Votes: 9
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Linux
Platform: PC
URL: http://docs.jboss.org/richfaces/latest_3_3_X/en/tlddoc/a4j/jsFunction.html


Issue Links:
Duplicate
is duplicated by JAVASERVERFACES_SPEC_PUBLIC-672 Allow Ajax Listener for jsf.ajax.request Closed
Issuezilla Id: 613
Status Whiteboard:

cat2 frame size_medium importance_large draft


 Description   

> Almost every AJAX framework I know of allows you to
> simply execute a method on the server side, with or without params,
> and return a result.

JSF should support this behavior. Use cases include:

  • Calling a server-side method to return values used to control page behavior.
  • Calling a server side method to submit data to the application, returning
    success, failure, or nothing to the UI.

This functionality is already part of the JBoss Ajax4JSF framework, every PHP
ajax framework, and every non-server tech-specific framework (such as Dojo,
Prototype, etc..)

See A4J:jsFunction component –
http://docs.jboss.org/richfaces/latest_3_3_X/en/tlddoc/a4j/jsFunction.html



 Comments   
Comment by Ed Burns [ 21/Aug/09 ]

Sure, I'll entertain this.

Comment by Ed Burns [ 24/Sep/09 ]

Move to unscheduled target milestone

Comment by Ed Burns [ 25/Sep/09 ]

Retarget to 2.next

Comment by Ed Burns [ 24/Nov/09 ]

Prepare to delete "spec" subcomponent.

Comment by Ed Burns [ 14/Dec/09 ]

Move these to unscheduled because we need to target them correctly. 2.next isn't
specific enough.

Comment by lincolnbaxter [ 26/Jan/10 ]

Categorized as part of Rev 2.0 A prep

Comment by rogerk [ 05/Mar/10 ]

cat2 - yes - this would be nice!

Comment by Ed Burns [ 22/Mar/10 ]

frame

Comment by Ed Burns [ 15/May/10 ]

These are targeted at 2.1.

Comment by Ed Burns [ 08/Jun/10 ]

triage

Comment by Ed Burns [ 22/Jun/10 ]

rogerk

Comment by rogerk [ 29/Jun/10 ]

target

Comment by rogerk [ 01/Jul/10 ]

re-target

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.

Comment by Manfred Riem [ 01/Aug/14 ]

Setting priority to Critical

Comment by balusc [ 21/Mar/16 ]

Blocked by https://java.net/jira/browse/JAVASERVERFACES-4115

Comment by balusc [ 27/May/16 ]

Pushed: https://java.net/projects/mojarra/sources/git/revision/26d852d26ce088e29eb414cb892263ac62278c42

It's available as <h:commandScript>, which is largely based on OmniFaces <o:commandScript>.

Will close when tests succeed.

Generated at Fri Jan 20 13:21:59 UTC 2017 using JIRA 6.2.3#6260-sha1:63ef1d6dac3f4f4d7db4c1effd405ba38ccdc558.