Comments on: EJB maintains its dominance

By: vin

vin — Fri, 19 Jun 2009 19:07:24 +0000

Spring is so much lightweight and easier and the IOC can be used even outside an EJB container. EJB still remains bloated, even with EJB 3.0. Applying lipstick to a pig doesn’t make it a fairy

By: Red Hat Magazine | Who wrote about JBoss World

Red Hat Magazine | Who wrote about JBoss World — Thu, 02 Apr 2009 19:30:25 +0000

[...] EJB maintains its dominance [...]

By: It’s not 2002 « Exit Condition

It’s not 2002 « Exit Condition — Thu, 04 Dec 2008 11:47:38 +0000

[...] data. Until then, I’m relegated to hold the position that EJB is maintaining its dominance[11]. Not to mention that even today JEE hasn’t yet shaken the bad blood accumulated in the [...]

By: Red Hat Magazine | Who wrote about JBoss World

Red Hat Magazine | Who wrote about JBoss World — Fri, 15 Aug 2008 15:30:13 +0000

[...] EJB maintains its dominance [...]

By: billburke

billburke — Tue, 19 Feb 2008 14:29:42 +0000

Mark, I believe if the right people get on these committees you can really change things. EE5 was JBoss’s first foray into specification work. It took a huge battle to get JPA (and thus Hibernate) standardized and finally we have a string persistence model in EE while at the same time unifying Hibernate, JDO, and CP crowds.

I don’t think open source is isolation enough. We need standards so that new players can push the old.

And no what I mean by core middleware is: persistence, transactions, messaging, caching, networking (web server/remoting). Everything else is just putting a pretty face on these core technologies. Even when it is a specification.

By: Mark Fisher

Mark Fisher — Tue, 19 Feb 2008 03:16:30 +0000

Bill,

I guess it’s just a difference of opinion, but I personally don’t understand the infatuation with standards for the sake of standards. My opinion on that matter changed at some point around the EJB spec’s 2nd attempt at CMP. When I consider EJB3′s @Interceptor approach, I can’t say that things have gotten any better. Anyways, Spring provides a model that allows developers to focus on business logic that is isolated from the infrastructure, and in my mind, that is the defining characteristic of middleware. Clearly, a growing community of developers recognize that the Spring portfolio offers pragmatic solutions beyond standards and specifications (Web Services, Security, Batch, etc). On the other hand, I’m pretty sure that your definition of “core middleware” assumes implementation of a specification as a requirement, and therefore this is a circular argument.

-Mark

By: billburke

billburke — Mon, 18 Feb 2008 05:35:52 +0000

Mark, please enlighten me on what core middleware service Spring implements? (or EJB for that matter). Spring isn’t even a full fledged kernel and needs OSGi to fill the gaps. This is what I mean by kiddy. A bunch of low hanging fruit that anybody could implement. Still, Java EE needs a kiddy layer to make it sexy, usable, and integratable. Right now we have a fracture in which one side is standards based and the other controlled by one commercial/VC driven company. I’ll choose and fight for standards every time.

By: openBlog » Spring vs Jboss war continues

openBlog » Spring vs Jboss war continues — Mon, 18 Feb 2008 04:59:21 +0000

[...] ago, I wrote about an Open Source War? Spring+Tomcat vs Jboss, which seems to continue in this post written by Bill Burke. The battle ground is EJB, that’s why it looks like Spring or EJB. However, I believe [...]

By: Mark Fisher

Mark Fisher — Sun, 17 Feb 2008 04:32:47 +0000

Bill,

Don’t you think it’s a bit paradoxical to imply that standardizing Spring would be “making Java EE better” while simultaneously calling it a “kiddy wrapper”? To be honest, as a core Spring committer trying to provide the best possible environment for developers while recognizing deficiencies in the EJB 3 specification, I take offense at such comments. Perhaps you can provide some enlightenment?

-Mark

By: joris wijlens

joris wijlens — Sat, 16 Feb 2008 10:01:57 +0000

I agree with the last two posts. I both used spring and ejb 3.0 I like both and I am in debt to such good programmers that provided me with high quality, free to use frameworks. But I what I don’t understand is that the people that created such good software (far better than I can), show such unprofessional behaviour towards each other. I had hoped for more collaborative behaviour at least a constructive discussion. These kind of discussions (I’ve seen more of these lately) don’t benefit us at all I think.

Peace (to quote another well respected colleague of ours)