jakartaee / jakartaee/faces

Faces Flows CDI Bean Defining Annotations Clarification

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

Nobody has claimed this yet.

Component: Flow Priority: Major Type: Bug
Dominant language
Java
Stars
127
Forks
59
Avg merge
23h
Merged PRs (30d)
7

Description

The Faces Flow annotation @FlowScoped is clearly defined as a CDI scope. In the CDI spec, however, it's not defined as a "bean defining annotation" [http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations](http://docs.jboss.org/cdi/spec/1.2/cdi-spec.html#bean_defining_annotations)

The default bean discovery mode is "annotated", so it seems that with the default CDI configuration @FlowScope beans aren't discovered. The beans are discovered correctly with a bean-discovery-mode="all", which is set via beans.xml

Is it desirable to require this kind of explicit configuration, which can possibly lead to confusion?
#### Affected Versions
[2.2]

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 comparing Faces' @FlowScoped definition with the CDI 1.2 bean defining annotations and the default annotated discovery mode. Reproduce discovery with the default configuration and with beans.xml set to bean-discovery-mode="all"; the issue is resolved when the required behavior or specification clarification is agreed and recorded.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.