You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an extension can obtain the list of all beans from the BuildExtension.BuildContext and filter it manually. It could be useful (and more efficient) to provide some query API, e.g. to find all beans that have a specific type in the set of bean types.
The text was updated successfully, but these errors were encountered:
- convenient Stream wrapper that can be used to filter beans
- allow for inspecting removed beans in BeanDeploymentValidator
- also make it possible to mark a synthetic bean as unremovable
- resolvesquarkusio#5653
- convenient Stream wrapper that can be used to filter beans
- allow for inspecting removed beans in BeanDeploymentValidator
- also make it possible to mark a synthetic bean as unremovable
- resolvesquarkusio#5653
mkouba
added a commit
to mkouba/quarkus
that referenced
this issue
Nov 29, 2019
- convenient Stream wrapper that can be used to filter beans
- allow for inspecting removed beans in BeanDeploymentValidator
- also make it possible to mark a synthetic bean as unremovable
- resolvesquarkusio#5653
- convenient Stream wrapper that can be used to filter beans
- allow for inspecting removed beans in BeanDeploymentValidator
- also make it possible to mark a synthetic bean as unremovable
- resolvesquarkusio#5653
Currently, an extension can obtain the list of all beans from the
BuildExtension.BuildContext
and filter it manually. It could be useful (and more efficient) to provide some query API, e.g. to find all beans that have a specific type in the set of bean types.The text was updated successfully, but these errors were encountered: