Specify that @javax.ejb.Asynchronous can be used instead of @Asynchronous in MP
See original GitHub issueSince @javax.ejb.Asynchronous
is already specified in the EJB spec and many MP implementations already provide it, I suggest to specify that it can be used instead of org.eclipse.microprofile.faulttolerance.Asynchronous
as an alternative. For many developers it could be confusing that there are 2 @Asynchronous annotations provided by an implementation and only one of them works. It’s very easy to use the wrong one.
In terms of TCK, a test would be executed only if @javax.ejb.Asynchronous
is on the classpath so that it passes or is ignored for implementations that don’t provide it.
Issue Analytics
- State:
- Created 6 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Asynchronous Method Invocation - The Java EE 6 Tutorial
Session beans can implement asynchronous methods, business methods where control is returned to the client by the enterprise bean container before the method ......
Read more >Asynchronous REST with JAX-RS and MicroProfile
In this post, we'll look at how to use asynchronous JAX-RS resource methods on the server side. There are limited use cases in...
Read more >EJB asynchronous methods settings - IBM
Specifies a default work manager instance. The product provides an internal work manager instance for support of EJB asynchronous methods.
Read more >Fire And Forget. Without JMS. With EJB 3.1 and 8KB WAR File
The method create returns Future, and can return so a result. It will either be executed in background thread or synchronous - if...
Read more >Correct way to use EJB Asynchronous methods - Stack Overflow
If you were using Java EE 7, you could use the @AccessTimeout(value = xx) annotation , but I think Websphere is Java EE...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I’m -1 on this.
It’s only an issue when those two annotations happen to be on the classpath, which is not the case with every MP implementation.
Also, it’s no different than the situation with other annotations in Java EE that are re-used between specifications.
-1 for me