jakartaee / jakartaee/faces

Allow refreshable ValueExpression for validator/converter/behavior tags

Open
#1,499 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
127
Forks
59
Avg merge
23h
Merged PRs (30d)
7

Description

Attributes on validators and converters are created and evaluated built time.
We may just need to introduce stateHelper like in components.

There are many workarounds in the past to support ValueExpression correctly for that cases:

  1. PrimeFaces behaviors:
    https://github.com/primefaces/primefaces/tree/master/src/main/java/org/primefaces/behavior/base
  2. MyFaces common converters
    https://cwiki.apache.org/confluence/display/MYFACES/MyFaces+Commons+Converters
  3. MyFaces commons validator
    https://svn.apache.org/repos/asf/myfaces/commons/trunk/myfaces-commons-validators/src/main/java/org/apache/myfaces/commons/validator/

also see:
https://issues.apache.org/jira/browse/MYFACES-3547
https://stackoverflow.com/questions/4439850/refresh-jsf-validator-attributes-on-rerender

Actually it's not a big feature, it just makes it easier to use and align the APIs with component attributes.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the PrimeFaces behavior implementations and the MyFaces Commons converter and validator implementations linked in the issue, then compare them with Jakarta Faces component state handling. Define how validator, converter, and behavior attributes should refresh and how that aligns their APIs with component attributes; the issue provides no specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
frontend, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.