|
|
|
|
|
|
by the_rosentotter
4065 days ago
|
|
|
> In modern Java EE there's no reason whatsoever to avoid EJB. I don't see much reason to use it, either. The only exception is for distributed transactions, where session beans serve as nice abstractions as entry points and managers for the transactions. |
|
|
For regular transactions (local, one transactional resource involved) they're still pretty handy as well. EJBs also have things like @Asynchronous, @RolesAllowed and the timer service. The @Stateless concept itself can be just the right abstraction as well.
Eventually though the EJB model will be decomposed and its services made available via CDI.
This is NOT because the EJB model is bad or unworkable, but because it makes sense to align everything on a single component model.