We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
I like to have a scope that is still available in methods I call that are annotated with @asynchronous.
Would it be possible to write a @AsynchronousScoped as outlined here https://www.knitelius.com/2016/04/18/pushing-ahead-on-concurrency-for-java-ee-8/ with the microscoped framework?
The text was updated successfully, but these errors were encountered:
I'm very interested on this, too. I have an heavy task, so I've annotated it with @Asyncrhonous but it looses the scope of the caller.
@Asyncrhonous
Sorry, something went wrong.
does https://deltaspike.apache.org/documentation/core.html#_asynchronous_operations help? loosing the caller scope is by design to not break scopes/code assumptions but ds would allow to propagate it with cdictrl probably
No branches or pull requests
I like to have a scope that is still available in methods I call that are annotated with @asynchronous.
Would it be possible to write a @AsynchronousScoped as outlined here https://www.knitelius.com/2016/04/18/pushing-ahead-on-concurrency-for-java-ee-8/ with the microscoped framework?
The text was updated successfully, but these errors were encountered: