Sun's recent confirmation that it has scrapped plans to make Java an international standard has put a damper on the company's coming out party for a new enterprise edition of the technology. And some of Sun's strongest supporters are riled.
In fact, IBM and BEA Systems, key Java boosters, recently said they have yet to sign licensing deals for the new Java 2 Enterprise Edition (J2EE). J2EE adds a vital set of interfaces and services for building server-based applications.
A lack of vendor support for a common version of Java would be bad news for customers, who would have less assurance that a Java program written for one application server would run on another.
While IBM and BEA say they will probably sign on to support J2EE, they still have issues to address with Sun regarding the firm's control over Java.
"We were a bit surprised by Sun's decision," said a deadpan Sandy Rankin, IBM's director of Java software. "The ball is really in Sun's court now; we're interested to hear about what they see are the alternatives to accomplishing this goal of a Java standard."
Ironically, it was IBM refugee Pat Sueltz, the recently appointed president of Sun's software and platforms group, who broke the news about Sun's decision during the Java Business Conference '99 in New York.
"We will remain the [Java] guardians," Sueltz said, noting that the European Computer Manufacturers' Association (ECMA) -- the group Sun has been working with since May to standardise Java -- hadn't done anything wrong. Sun's decision had more to do with the company's commitment to control compatibility among various Java-based products and to speed Java development, she said.
However, observers say Sun's relationship with the ECMA became strained because of the group's policy of not maintaining a vendor's copyright and Sun's insistence on not giving up its Java copyright.
But Sun hit a few high notes of its own at the conference. Among those was the company's decision to do away with certain royalties it had been extracting from Java developers.
And even Sun's decision on yanking Java out of the ECMA's hands wasn't considered bad news by all Sun partners.
"Long term, we think it would be beneficial to the industry to turn Java over to a standards body," said John Magee, Oracle's director of Internet platform marketing. "But we're comfortable with the decision on ECMA because the process [created by Sun for developing the Java specification] has been working very well."
The system he refers to is the Java Community Process, under which anyone can propose a change to the Java specification. A Sun "program office" reviews proposals and invites members of the Java development community to work on turning approved proposals into drafts that are then used by Sun engineers to build new Java code.
The ECMA decision got mixed reviews from users. Without copyright protection, Sun would be unable to go to court to prevent other companies from creating incompatible Java Virtual Machines or other software, said independent Java consultant Rajeev Karunakaran.
"If making Java a standard means it becomes easier for Microsoft to create a divergent form of Java, then I think Sun's decision was right," he says.