Clarify bean ordering when iterating over an instance #42949
Conversation
|
I also created a discussion in CDI to see if it's relevant to include this in the spec: |
This comment has been minimized.
This comment has been minimized.
| @@ -957,6 +957,27 @@ Alternatively, you can use the `@LookupIfProperty` and `@LookupUnlessProperty` a | |||
| } | |||
| ---- | |||
|
|
|||
| if there is more than one bean that matches the required type and qualifiers and is eligible for injection, it is possible to iterate (or stream) available bean instances. | |||
There was a problem hiding this comment.
I think that this paragraph would deserve a separate section with title along the lines of "Sorting beans obtained with programmatic lookup".
There was a problem hiding this comment.
I agree, I'd add it as a separate non-standard feature.
Ideally with a use case (why you might need it) and with an example showing two prioritized beans (and third with no prio?) and what the ordering looks like.
There was a problem hiding this comment.
@mkouba , just updated the PR, WDYT ?
rmanibus
force-pushed
the
bean_ordering_doc
branch
2 times, most recently
from
035b7b3
to
4c79973
Compare
|
🙈 The PR is closed and the preview is expired. |
This comment has been minimized.
This comment has been minimized.
Co-authored-by: Guillaume Smet <[email protected]>
rmanibus
force-pushed
the
bean_ordering_doc
branch
from
4c79973
to
1870f6c
Compare
Status for workflow
|
cc @mkouba