[javaee-spec users] [jsr366-experts] Re: Re: One container to rule them all

From: Antonio Goncalves <>
Date: Fri, 20 Feb 2015 17:11:15 +0100

Take @Stateless and replace it with a @Transactional, and that's the end of
the EJBContainer API. Either we update it with the new improvements of Java
EE 7 and 8, or we leave it. Nobody uses the EJBContainer in "real"
applications, not even for testing as we quickly can't make it work with
other specs. A Container that is allowed to orchestrate all the other
specs, makes sense, if it's only a subset (like the EJBContainer) then it
will not be used.

Except for the front-end technologies (JSF and JSP) I would like to have a
Container API to rule them all.


On Fri, Feb 20, 2015 at 4:55 PM, David Blevins <>

> On Feb 20, 2015, at 7:20 AM, Antonio Goncalves <
>> wrote:
> > and is completely useless today
> Careful about that. Bill's biggest concern with Java EE in general is
> adding things which immediately become failed and legacy.
> That statement will read, "we couldn't figure out how to make an EJB
> Container API people wanted, let's take our lack of skill and make a
> Container API."
> They frequently let the sub-specs have a little creative freedom as a way
> to test interest and the market for ideas that might make sense platform
> wide.
> If the EJB Container API is successful. More will come.
> If it was failed. The train stops entirely.
> -David

Antonio Goncalves
Software architect, Java Champion and Pluralsight author
Web site <> | Twitter
<> | LinkedIn <> |
<> | Paris
JUG <> | Devoxx France <>