JSF: skip looking for managed/named beans on incompatible JSF versions

[NicolaIsotta]

• do not search CDI Named beans on JSF 2.1- (CDI support was introduced in 2.2)
• do not search managed beans on Faces 4.0 or upper since support was removed

small code refactors/modernization

---

^Add meaningful description above

Click to collapse/expand PR instructions

By opening a pull request you confirm that, unless explicitly stated otherwise, the changes -

• are all your own work, and you have the right to contribute them.
• are contributed solely under the terms and conditions of the Apache License 2.0 (see section 5 of the license for more information).

LLMs, Commit messages and PR description:

• Please make sure (eg. git log) that all commits have a valid name and email address for you in the Author field.
• LLM assisted commits should be attributed with an Assisted-by: MODEL_NAME MODEL_VERSION line appended to the commit message.
  • Please mention coding assistance in the PR description too (eg. by adding the same Assisted-by line from above)
  • Please describe the changes in your own words - we'd like to know you understand the changes being made!

If you're a first time contributor, see the Contributing guidelines for more information.

If you're a committer, please label the PR before pressing "Create pull request" so that the right test jobs can run.

PR approval and merge checklist:

1. Was this PR correctly labeled, did the right tests run? When did they run?
2. Is this PR squashed?
3. Are author name / email address correct? Are co-authors correctly listed? Do the commit messages need updates?
4. Does the PR title and description still fit after the Nth iteration? Is the description sufficient to appear in the release notes?

If this PR targets the delivery branch: don't merge. (full wiki article)

[NicolaIsotta]

Just a note: the current behavior doesn't actually cause errors or exceptions - the main purpose of the PR is performance

[mbien]

@NicolaIsotta this looks like a small change and I suppose you tested it. If you want we could try merging this for NB 31 if you rebase it soon (till Wednesday)

[matthiasblaesing]

@NicolaIsotta I'm wondering about the statements, that check for the JSF version. The current implementation is mixed in regard to beans to be not shown if the version can't be determined:

• JsfELVariableResolver return beans based on ui:param if version can't be determined
• WebBeansELVariableResolver does not return beans if version can't be determined
• JSFBeanCache does not return beans if version can't be determined.

Would it make sense to unify this?!

[NicolaIsotta]

Makes sense, I'll align the behaviors

BTW: this is just a small performance improvement, I think it can safely wait NB32

[NicolaIsotta]

Updated and rebased, ready to merge

[NicolaIsotta]

Suggestion applied. Re-tested with 2.3 and 4.0 jsf projects, bean resolution looks on both.