|Re: [ee4j-community] Tomitribe commitment to EE4J|
We tend to be passionate about topics we perceive as abandoned. Before we sign ourselves up for any crusades, we would like community feedback to see if there are other's who might share our passions.
EJB: We believe CDI is the future and all things should align to it. We (Java EE EG, EJB EG) started work on aligning EJB to CDI in the form of breaking apart the EJB spec into smaller specifications like Interceptors specification and @Transaction specification, but we did not finish. There is some work left pulling things like @Schedule, @Asynchronous, or @Lock(READ) out.
The former EJB should just be services that could be applied to any CDI bean.
In JSR 375 we (EG) unfortunately did not go into any aspects of modern rest security, which is a real shame.
The specification is a step forward, but does fall into the same trap that Java EE security has always "solved" the via Java layer abstractions and doesn't address wire level interoperability.
What was done in the MicroProfile JWT specification should get merged in some way with EE4J security. Microservices should be able to portably communicate the caller via JWTs.
There is some internal tribe interest in participating in JCA, JPA and JAX-RS. For JPA, there are thoughts about what a Java 8 stream based API for JPA might look like.
On the topic of RIs, we would want the ability to chose the RI for anything we might lead. Before any "that's the way it is" might be used as an argument, we'd point out that we are changing almost everything about EE and its process. We'd want to see this up for discussion.
Back to the top