---

Java Application Support

Radar #4443822

EOModeler incompatible with J2SE 5.0

Description:

Older versions of the EOModeler application, bundled with WebObjects, are incompatible with J2SE 5.0 Release 4.

Workaround:

EOModeler needs to be forced into using Java 1.4.2. To do this, open its Info.plist file (located in EOModeler.app/Contents/) and change its JVMVersion key to 1.4*.

Radar #4413220

Borland JBuilder 2005 incompatible with J2SE 5.0 Release 4

Description:

JBuilder 2005 update 4 added Borland's own implementation of the AWT classes based on Java 1.4.2. Concurrently, JBuilder uses a custom launcher that loads the VM using the CurrentJDK link. Since the VM is running J2SE 5.0 but the actual AWT classes are from Java 1.4.2, an exception is thrown.

Workaround:

This issue is unresolved at this time. Reverting to an older version of JBuilder 2005 is known to work.

Radar #4430398

OpenBase JDBC and J2SE 5.0

Description:

Database transactions with OpenBase fail with strange data mapping errors.

Resolution:

Download the latest J2SE 5.0-compliant OpenBase JDBC driver at http://www.openbase.com.

---