The delayed Java 2 Enterprise Edition (J2EE) 1.4 specification has reached completion, but not without stumbling at one of the final hurdles.
Members of the Java Community Processes (JCP) J2EE executive committee have unanimously approved the 1.4 platform reference implementation (RI) and test compatibility kit (TCK).
However, one company – IBM Corp [IBM] – has voiced disquiet at J2EE 1.4’s licensing terms. All other members of the 16-strong committee made no comment on licensing.
The company’s objection belies what some consider an undercurrent of tension between IBM and JCP members, particularly Sun Microsystems Inc [SUNW], over certain issues.
Historically, IBM voted against inclusion of the Java Messaging System (JMS) in J2EE 1.3 in a move some claim was designed to protect IBM’s MQ middleware business. IBM justified the move by saying JMS added another calling service API to J2EE, which complicated the structure.
More recently, Sun has changed some of J2EE’s licensing so developers can deploy using the RI, regarded as an application server.
J2EE 1.4 enjoys a drawn-out history. Due in the second half of 2002, 1.4 was delayed once to include Web Services Interoperability (WS-I) organization’s Basic Profile 1.0, and then delayed again, once the WS-I’s work slipped. J2EE 1.4 is now roughly a year and a half late.
This article was based on material originally published by ComputerWire.