-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Method invokers #460
Comments
Perhaps inspiration can be taken from Micronaut here as an implementation of this proposal effectively exists there already:
|
When we get to this, I believe it would be great if this API supported providing an initial context data map for eventual interceptors ( |
I just submitted an initial proposal for this: #639. |
The initial proposal was merged and will be part of the first Alpha for 4.1. TCK tracking issue - jakartaee/cdi-tck#491 |
The specification and TCK for this are done. We ended up removing transformers and wrappers from CDI 4.1, those should get specified in a future version, but the main functionality is there. |
(copied from CDI.Next doc, as there was no issue yet to track this)
Currently CDI does not have a concept of a bean method that can be executed from another bean with parameter binding.
Such a concept is used in other specs, such as JAX-RS, where resource methods are executed at runtime with the need to bind their parameters, and provide the support for interceptors and other CDI features.
The CDI spec should add API for such a feature, so other specs do not need to define a custom solution.
The following should be possible:
Pseudocode:
Let’s consider the following bean:
Now we could create a parameter binder:
And the execution of this method would be something like:
The text was updated successfully, but these errors were encountered: