Vendors can now test for compatibility of open source Java 2 Enterprise Edition (J2EE) implementations using an official Test Compatibility Kit (TCK) without being required to also accept official J2EE code.
The changes are designed to avoid a situation where intellectual property (IP) of certain vendors that is contained in the J2EE code may be handed over to the open source community along with the TCK, raising potential future licensing issues.
We are being very diligent, said group marketing manager for Java and Sun One OEM licensing Rick Saletta. Minds have been concentrated on licensing of IP in the wake of SCO Group’s $1bn legal action for alleged IP infringement and anticompetitive activities against IBM.
The detachment of the TCK and J2EE code, though, are part of ongoing alterations to the Java Community Process (JCP), the body that stewards Java, designed to make its mechanisms and all-important TCKs friendlier and more available to open source organizations.
The intention to make changes was announced at JavaOne last year and were initiated following growing pressure from the Apache Software Foundation.
Sun said it now hopes open source organizations, such as JBoss Group LLC – maker of the eponymous J2EE application server – will achieve official J2EE certification and line-up against the open source and Java common enemy – Microsoft.
The changes, announced last week, come ahead of J2EE 1.4, whose publication is expected this summer. J2EE 1.4 wraps a number of existing Java APIs for integration and XML web services into the core platform.
We want to make sure everyone can work on the same web services standards, Saletta said. The competition for Java vendors is what ever Microsoft offers and it’s important we all maintain unity.
Source: Computerwire
