Monthly Archives: May 2012

Internet Explorer and ADF: Not Friends

One of the advantages to using commercial, fully supported framework like Oracle Application Development Framework (ADF) is that the vendor supplies a list of supported browsers. If something doesn’t work or doesn’t look right, it’s the vendor’s problem.

When we started a recent project, we initially made sure that our ADF 11.1.x pages looked OK in Internet Explorer and Firefox. As expected, no problems. So we started building our application, and the developers used Firefox and Chrome because of the superior tooling these browsers offer for web developers.

However, as has happened in other applications, one screen mutated into the dreaded “one-screen-to-rule-them-all” page allowing a power user to see and change almost every data item in the entire system. And while Firefox and Chrome were able to render our panels inside tabs inside panels inside accordions inside panels, Internet Explorer had to give up at some point.

Lesson learned:

ADF allows the developer to write cheques that Internet Explorer can’t cash. [tweet this]

Have your developers run their pages in IE every day in order to see where you meet the limitations of Internet Explorer. It’s much easier to fix the issues during development than during QA…

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.