• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Link to 1.3 Reference Implementation

 
author
Posts: 9050
21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
It seems Sun is trying to move us towards J2EE 1.4! Well, we're not quite ready yet
If you've had difficulty tracking down the 1.3 Reference Implementation, don't feel bad, Sun's kind of been hiding it
Here's the link, long live 1.3!
http://java.sun.com/j2ee/sdk_1.3/
Bert
 
Ranch Hand
Posts: 46
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I was browsing through "Java Community Process" home page and was surprised to see that EJB 3.0 might be released soon along with J2EE 1.5 (especially since there was more than 2 years of gap between EJB 2.0 and EJB 2.1).
The public review will be somewhere in June 2004.
Please refer the url below for more details :
http://jcp.org/en/jsr/detail?id=220
I really hope that they beef up EJB-QL. Currently the container providers are supporting lot of functionalities (dynamic queries, lazy loading, ..) using extension to EJB-QL (but then you get stuck with a vendor and takes you back to square 1). The best part here is that the major vendors BEA, Borland, Oracle and IBM are in this expert group , supporting it and lets hope that they all standardize on everything.
Some of the other aspects that are being tackled can be overcome now by using good J2EE patterns.
That may be the reason SUN is pushing out J2EE 1.4, since they have to push put J2EE 1.5 soon.

Peter
SCJP,SCJD,SCWCP,SCBCD,IBM-XML,MCP
[ February 16, 2004: Message edited by: Peter Vennel ]
 
Bert Bates
author
Posts: 9050
21
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The thing about J2EE is that Sun might push and push, but the vendors have to do a LOT of pulling to make a new EE fly. We did an informal (which of course translates to "highly suspicious"), survey about a month ago, and found that the major J2EE vendors weren't in any big rush to be J2EE 1.4 compliant - which makes sense, it's a BFD for them!
So let's say the big J2EE vendors get around to being 1.4 compliant later in 2004... then companies using J2EE have to take the plunge to upgrade to 1.4, which is yet another Big Deal. How long will it be before actual users would be using 1.5 ?
It seems it's a lot easier to evolve J2SE than J2EE...
 
Ranch Hand
Posts: 330
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Sun's kind of been hiding it



You're right. I just went to that site and after choosing a platform and clicked "ok" I get a "Bad Request" error message.

So does this mean I'm left with no option but to get the Sun ONE Application Server 7 (j2ee 1.3 compatible)?
 
Yes, of course, and I accept that blame. In fact, i covet that blame. As does this tiny ad:
a bit of art, as a gift, that will fit in a stocking
https://gardener-gift.com
reply
    Bookmark Topic Watch Topic
  • New Topic