Why J2EE1.4 and not J2EE1.5 ?

[Pho Tek]

J2EE1.5 was recently announced ? Why bother with J2EE1.4 when major changes are underway ?

[Theodore Casser]

Because who knows when J2EE 1.5 will come out.

You can't just wait for the next "better thing" to come along, or you're always going to be waiting. For instance, why develop with J2SE 1.5 when you know that 1.6 (or whatever they end up calling it) will be out in 18 - 24 months?

I'd just start with 1.4 and build from there, change as needed for 1.5, etc.

[Alvin chew]

i believe j2ee1.5 only add some features, but the concept behind still the same ....

somemore for developer , it won't be so fast to switch for new technology as their might still using j2ee1.4 .

[somkiat puisungnoen]

I think,
J2EE1.4 is reference to J2SDK 1.4 so still use J2EE1.4

[Solveig Laura Haugland]

Originally posted by Pho Tek:
J2EE1.5 was recently announced ? Why bother with J2EE1.4 when major changes are underway ?

Because then the book never comes out and we never get any royalties. ;>

Also there's an all but physical urge to heave a book out after a certain point, like the birthing process.

And, the most important reason is that J2EE 1.4: The Big Picture is not about having the latest details. It's about having the understanding of what a container is, what entity beans can do for you, what a transaction is. The version of the spec is less relevant when that's the main goal.

Solveig
~~~~~~~~~~~~~~~~
[e-mail]
www.bigpicture-books.com

www.bigpicture-books.com/bigpicturetoc.pdf

"J2EE: The Big Picture" by Solveig Haugland, Mark Cade, and Anthony Orapallo
Knowledge without coding.
Understanding without boredom.
And occasional references to badgers.