01 August 2004 - java_dev (original) (raw)

I've picked up this book.

I think its great so far. I've really bought into the whole simplicity of j2ee
methodology, rather than the 'lets code these mammoth EJB/container apps just
for the what if factor'.

I've very much experienced this at work. There are always those questions of
What if we need this, or What if we decide to do that. Those things could be
changing database vendors, to changing the hardware we run on.

In real life, how often have any of you really done that. We are an Oracle shop at work. What are the odds that someone is going to come along and say "We are gonna
switch to DB2 next week, or SQLServer". Pretty much nil. That's not exactly the
best example. The point is, why should we spend all this extra money/time
developing and tying ourselves to a container when we really should focus
on coding to interfaces and be agile. If something comes up (and that's a big
far fetched if), then refactor to meet the need.

So, how many of you are on the fence about EJB? How many are on the side of the
fence fully supporting always using them? How many of you are the side that
utilizes hibernate and spring and AOP? Oh, and how many of you have no clue what
I'm babbling about? :)

-k