Rickards comments on the J2EE container shootout.
Rickard's comments on the shootout and the war.
Rickard Öberg has posted some great comments on the J2EE Container Shootout. Before you get to the J2EE Container Shootout comments, keep an open mind as you read Rickard's comments on Bush's "war on terror" - like it or not, this is how we Americans look to some of our best allies.
[Blogging Roller]
Great comments from Rickard Öberg and I agree with all of them. Servlets and Web Services are the future, I already view EJB as legacy. [James Strachan's Radio Weblog]
It is kind of weird, sitting on the sidelines during the growth of ejb. I have some how always wound up on some project that was being done using traditional servlets and jdbc, "because we don't have time for that airy-fairy j2ee stuff on this project". The next project, however, was always going to be the all singing, all dancing, BEA based J2EE killer development project.
I need to learn EJB, because I can't get java work in sydney without it anymore (unless I want to work at technologically retarded large corporates for the rest of my programming career).
So, I am going to play dumb here again (probably because I'm good at it), and ask: Why is ejb now legacy?
I'll be the first to admit the AOP is cool, in that you can make small peices of code have far reaching (nay, magical) effects. I'll readily admit that XDoclet, and other code generation tools, save hours of coding. I'll happily accept that Web Services are an essential ingredient in our coming interconnected world.
But doesn't EJB still serve as a useful business object implementation strategy? Combine a object heirarchy encapsulating business rules, with a half decent cmp system, and you have the back end data repository for your web services right?
Or have I completely missed the card trick?
12:23:43 AM
|