Details

    • Type: New Feature New Feature
    • Status: Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None

      Description

      Currently component referencing with the JSF API is very limited.
      Keywords can currently only be used with f:ajax and not for e.g. outputLabel "for" attribute.
      Also keywords cant be combined and we dont even have many keywords.

      For PrimeFaces, i created a small modular API to enhance the search alogorithm as you can read here:
      http://blog.primefaces.org/?p=2740

      Noteable features are:

      • keywords can be used for all components
      • combinable keywords like @composite:@parent or @form:myId
      • currently a (limited) pluggable framework to allow new keywords for endusers

      For the JSF API, a new artifact for resolving expression for findComponent (like ViewHandler etc.) would be great and can easily be enhanced by component libraries.
      Maybe something like "ComponentExpressionResolver".

      If its somehow possible, i would like to help to create and finalyze the API.

      Sorry for Issue 1237 - please close it.

      1. 20170113-1208-2_3_x-wls-12_2_1-development-fss-client.txt
        3.09 MB
        Ed Burns
      2. 20170116-0432Z-JAVASERVERFACES_SPEC_PUBLIC-1238.diff
        310 kB
        Ed Burns
      3. AjaxBehaviorRenderer.java
        14 kB
        Ed Burns
      4. changebundle.txt
        1 kB
        Ed Burns
      5. changebundle.txt
        4 kB
        Ed Burns
      6. spec-1238.diff
        303 kB
        Ed Burns
      7. spec-1238-20170114.diff
        0.7 kB
        Ed Burns

        Activity

        Hide
        Ed Burns added a comment -

        Thanks Arjan, yes it was that test that failed. But I don't want to exclude it on WLS. It should run on WLS if it is a truly backward compatible change, which it must be since it is not hidden behind a context param.

        Show
        Ed Burns added a comment - Thanks Arjan, yes it was that test that failed. But I don't want to exclude it on WLS. It should run on WLS if it is a truly backward compatible change, which it must be since it is not hidden behind a context param.
        Hide
        Ed Burns added a comment -

        Ok, commit 3ab4cf8 has the fix that passes all tests. If it breaks the build this time, it is possible we may not have this feature in JSF 2.3.

        Show
        Ed Burns added a comment - Ok, commit 3ab4cf8 has the fix that passes all tests. If it breaks the build this time, it is possible we may not have this feature in JSF 2.3.
        Hide
        Ed Burns added a comment -

        Built with

        webapp.projectStage=Development
        webapp.stateSavingMethod=server
        webapp.partialStateSaving=false
        webapp.serializeServerState=false

        Show
        Ed Burns added a comment - Built with webapp.projectStage=Development webapp.stateSavingMethod=server webapp.partialStateSaving=false webapp.serializeServerState=false
        Hide
        Ed Burns added a comment - - edited

        Commit dcca156 has the @Ignore of the failing tests.

        Show
        Ed Burns added a comment - - edited Commit dcca156 has the @Ignore of the failing tests.
        Hide
        Ed Burns added a comment -

        Commit c1eff0f removes the @Ignore and reverts the change that was causing them to fail.

        Show
        Ed Burns added a comment - Commit c1eff0f removes the @Ignore and reverts the change that was causing them to fail.

          People

          • Assignee:
            Ed Burns
            Reporter:
            tandraschko
          • Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated: