[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
|
I do agree, it's just that I think @Service is actually better semantics for @Stateless. I think something like @Service fits nicely as a common annotation/service supported by the platform.
Even if built in, the other benefit of stereotypes is that they are very self-documenting. I always have trouble explaining to beginners exactly what @Stateless does.
Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
-------- Original message --------
From: John Hogan <jhogan515@xxxxxxxxx>
Date: 10/16/17 2:18 PM (GMT-05:00)
To: EE4J community discussions <ee4j-community@xxxxxxxxxxx>
Subject: Re: [ee4j-community] Deprecating EJB in Favor of CDI Services
Ok, but I'd rather not because that is more work, and we still haven't achieved what @Stateless provides.
At this point, I don't miss any ejb features because they're still there. That being said, in the future, it would be desirable to not need to reinvent special stereotypes to get back what ejb provides today. I believe that if something is not broken then it doesn't need to be fixed. If the plan is to fix it anyway, whatever comes next should provide equivalent functionality without needing to do a bunch of new work coding TXs ... I like the power, simplicity and convention over configuration nature of ejb. A major goal and focus of Java EE has been on ease of use and improving programmer productivity. I think that should remain as a design philosophy and goal number one.