Is JDeveloper 11.1.2 a Dead End?

Oracle recently came out with JDeveloper 11gR2 (11.1.2.x), and not everyone was impressed. See for example the discussion “Performance and stability of JDeveloper 11gR2 vs. 11gR1” in the ADF Enterprise Methodology Group.

If you look up JDeveloper 11gR2 in the Oracle Lifetime Support Policy document, on page 9 you will find that 11gR2 does not get the normal 5 years of premier support and 3 years of extended support. Instead, you have only 3 years of premier support, ending June 2014. In effect, Oracle does not consider JDeveloper 11gR2 a real release and will only support it as long as they support 11gR1.

Finally, if you look at the section “Bugs Fixed in” in “Oracle JDeveloper and Oracle ADF 11g Release 2 (11.1.2.x) New Features”, you see a lot of bugs where the subject start with “backport”. Backporting means to take a bug fix from a newer release and apply it to an older one. So the fact that the very latest JDeveloper release comes with backports right from the start indicates that Oracle is considering 11gR2 the “old” release.

JDeveloper 11gR2 looks like a dead end in ADF development [tweet this]

Would you consider using it? Please comment below.

4 thoughts on “Is JDeveloper 11.1.2 a Dead End?

  1. Hi Sten

    For the record as explained at Oracle Open World 2011 there are 2 current publicly available for JDev, 11.1.1.X.0 (11gR1 – currently is the max version of this branch) and 11.1.2.X.0 (11gR2 – currently is the max version of this branch).

    There are 2 core differentiations between 11gR1 vs 11gR2:

    1) 11gR2 supports the newer JSF2.0, while 11gR1 supports JSF1.2. The 11gR2 release was brought out for customers who didn’t want to wait for 12c and wanted the JSF2.0 functionality now.

    2) Only 11gR1 will support the FMW stack. There will be no FMW release on 11gR2, only 11gR1 (and the eventual 12c full release of course).

    There are definitely “backport” patches flying around between the branches, and indeed 12c is backfilling fixes across the versions too. Expect a and a sometime in the future (as per the roadmap).

    So to summarize which versions should customers go with?:

    a) If you don’t care about JSF2.0 support, or you need the rest of the FMW stack, 11gR1 is for you

    b) If JSF2.0 support is what you want, go with 11gR2

    Once 12c becomes available, that will be the natural choice as all branches will converge.

    There is a “c” too, you can stay on 11gR1 but port your application to 11gR2 to purely test how well it runs under JSF2.0. For customers who have automated regression testing this is an example where such an investment in testing will now handsomely pay off.

    Finally in my honest opinion (not necessarily Oracle’s) staying on 11gR1 is the smart thing to do as you’ve strategically aligned with Oracle’s current Fusion App developments. As they find bugs they’ll be fixed in 11gR1 first, then possibly backported 11gR2 (resources pending).



  2. One of the advantages of JSF 2.0, and therefore ADF is that it is better behaved with non-Oracle component libraries. I’ve used the Apache MyFaces Tomahawk library for one project, and we are currently using the reporting tool, Eclipse BIRT with the jsf4birt library in a development project.

Comments are closed.