JDeveloper versions supported by JHeadstart 11g (11.1.1.x) and 10g (10.1.3.x)

December 2008

This matrix shows JDeveloper versions that are compatible with JHeadstart 11.1.1.x and 10.1.3.x versions. For compatibility with Application Servers, please see the JDeveloper / Application Server Support Matrix, and the Deployment category of the JHeadstart Blog.

To use this matrix:

• Find the cell corresponding to the version of JHeadstart you want to use and the JDeveloper version you want to install it in.
• The contents of the cell tell you whether this combination is supported, and what, if anything, you need to do to make it work.

Notes

1. You need to rename velocity-dep-1.3.jar to velocity-dep-1.3.jar.backup in JDEV_HOME/jdev/lib before you can use JHeadstart. See the JHeadstart Release Notes, section Known Issues, for more info.

2. JDeveloper needs to have at least Service Update 2 installed. You can install service updates using the JDeveloper Check For Updates feature in the Help menu. First install Service Update 1, then install the highest available Service Update. See the JHeadstart Release Notes, section Compatibility, for more info.

3. There is a caveat if you generate file upload in your JHeadstart application. You need to install JDeveloper Patch 5623059 (you will be required to create an account to log into MetaLink).

4. The reason this combination is not supported is an incompatibility with the JAXB libraries that are installed as part of the new WebCenter extension in JDeveloper. This library conflict causes problems when using the JHeadstart design-time tools like the New Application Definition Wizard and the Application Definition Editor. There are no problems at runtime, JHeadstart-generated applications run fine with the JDeveloper ADF runtime libraries. There is a work around though: you can copy the JAXB libraries in the JHeadstart extensions directory JDEV_HOME\jdev\extensions\oracle.jheadstart.10.1.3\designtime\lib to the WebCenter extensions directory JDEV_HOME\jdev\extensions\oracle.portlets.10.1.3\lib. Make sure you backup the original WebCenter JAXB libraries first! Note that when you copy the JHeadstart JAXB libraries, the Portlet Producer Wizard will no longer work as expected! In other words, you cannot use JHeadstart and Webcenter within the same JDeveloper session. You will have to copy back and forth the JAXB libraries and restart JDeveloper when you want to switch between JHeadstart and WebCenter applications. Alternatively, you can create two JDeveloper installations, one for WebCenter development, and one for JHeadstart development.

5. JDeveloper 10.1.3.0 ships with an older version of the xml jar file than the one installed with JHeadstart 10.1.3.1 and higher. This library conflict results in the Application Definition Editor not working properly: copying and moving items does not work. To use the correct xml.jar library shipped with JHeadstart, you must close JDeveloper and rename xml.jar in JDEV_HOME/lib to xml.jar.backup. Then copy the xml.jar from JDEV_HOME/extensions/oracle.jheadstart.10.1.3/designtime/lib to JDEV_HOME/lib.

6. JDeveloper 11.1.1.0 ships with a version of the Oracle XML Developers Kit that contains bug 6446136: XDK SCHEMA VALIDATION IS NOT THREADSAFE DURING NCNAME VALIDATION. You can run into this bug when generating Page Definitions (ADF Model Bindings) in JHeadstart. It results in popup errors with an oracle.bali.xml.model.XmlInvalidOnCommitException, and the resulting PageDef file is incomplete.
A patched version of xmlparserv2.jar in which this bug is fixed, is shipped with JHeadstart. To install this patch:

• Close JDeveloper

• Rename xmlparserv2.jar in JDEV_BEA_HOME/jdeveloper/modules/oracle.xdk_11.1.1 to xmlparserv2.jar.backup

• Copy the xmlparserv2.jar from JDEV_BEA_HOME/jdeveloper/jdev/extensions/oracle.jheadstart.11.1.1/designtime/lib to JDEV_BEA_HOME/jdeveloper/modules/oracle.xdk_11.1.1