Issue Details (XML | Word | Printable)

Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: rogerk
Reporter: lu4242
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.

tlddoc says f:ajax event - type="javax.el.ValueExpression (must evaluate to java.lang.String)", but in theory that is invalid

Created: 23/Jul/11 05:47 PM   Updated: 25/Jul/11 04:17 PM   Resolved: 24/Jul/11 05:42 PM
Component/s: Documentation: Javadoc, TLDDoc, RenderkitDoc, PDF
Affects Version/s: None
Fix Version/s: None

Time Tracking:
Not Specified

File Attachments: 1. Text File changebundle-spec-1026.txt (0.8 kB) 24/Jul/11 05:34 PM - rogerk

Participants: 120430, lu4242, Martin Kočí and rogerk

 Description  « Hide

JSF 2.0 spec facelets tlddoc says on f:ajax "event" property that it can be assigned to a ValueExpression, but in theory that is not possible. The documentation of vld.retargetAttachedObjects call getEvent() without pass FacesContext, so I suppose this is a bug on the documentation. Related issue on MyFaces is MYFACES-3233

Martin Kočí added a comment - 24/Jul/11 09:05 AM

it would be nice to have support for event=ValueExpression

<f:ajax event="#{user.preferredEvent}" >

-> user can select if he/she want keyup or change for example. This is useful is use case like "perform validation during typing" and "perform validation after cursor leaves the field"

Currently wen need two same f:ajax element with different event names and disable one with disabled="#{}"

rogerk added a comment - 24/Jul/11 05:34 PM


rogerk added a comment - 24/Jul/11 05:42 PM

Committed to trunk:
Sending jsf-ri/conf/share/facelets_jsf_core.tld
Transmitting file data .
Committed revision 9214.

Committed to MOJARRA_2_1X_ROLLING:
Sending jsf-ri/conf/share/facelets_jsf_core.tld
Transmitting file data .
Committed revision 9215.

120430 added a comment - 25/Jul/11 09:49 AM

I would agree Martin. Why ValueExpression should not supported?

rogerk added a comment - 25/Jul/11 10:45 AM

It should be supported. There is an open issue for it.

lu4242 added a comment - 25/Jul/11 04:17 PM

Do you know the issue? which number is it? just for reference purposes? will this be handled in JSF 2.2?