Sun Gets Tough with J2EE 1.4 Certification

Zardon · Mar 20, 2003, 08:23 PM

Time is running out for companies that have still not certified their platforms for J2EE v1.4, Sun Microsystems said Wednesday.

While the next incarnation of the enterprise-based operating environment is not due for release until later this spring, the Santa Clara, Calif.-based firm is cracking down on what it calls "renegade" vendors trying to pass themselves off as J2EE compliant.

For Sun, J2EE 1.4 represents its common language for Web services, which it needs to combat Microsoft's .NET platform.

"We want to tell our partners that licensing is now available and that they should complete their testing as soon as possible," Rick Saletta, group marketing manager, J2EE Licensing at Sun told internetnews.com. With previous versions of J2EE you got various compatibilities. That made it difficult for companies to get engaged. This was particularly a tricky situation with open source, which is why moving forward; we had to separate the licensing from source, from that of the test suite."

Internetnews

Mar 20, 2003, 08:23 PM	#1
Zardon DriverHeaven Founder Join Date: May 2002 Posts: 32,480 Rep Power: 179	Sun Gets Tough with J2EE 1.4 Certification Time is running out for companies that have still not certified their platforms for J2EE v1.4, Sun Microsystems said Wednesday. While the next incarnation of the enterprise-based operating environment is not due for release until later this spring, the Santa Clara, Calif.-based firm is cracking down on what it calls "renegade" vendors trying to pass themselves off as J2EE compliant. For Sun, J2EE 1.4 represents its common language for Web services, which it needs to combat Microsoft's .NET platform. "We want to tell our partners that licensing is now available and that they should complete their testing as soon as possible," Rick Saletta, group marketing manager, J2EE Licensing at Sun told internetnews.com. With previous versions of J2EE you got various compatibilities. That made it difficult for companies to get engaged. This was particularly a tricky situation with open source, which is why moving forward; we had to separate the licensing from source, from that of the test suite." Internetnews