X

Shay Shmeltzer's Oracle Development Tools Tips

  • November 10, 2009

JDeveloper 11.1.1.2 is out

Shay Shmeltzer
Director of Product Management - Oracle

A new version of JDeveloper is out on OTN - looking at the version number you might think this is just a patch release with some bug fixes, but in reality it is quite a major release for us.

The new features document should be here shortly.

In the meantime, some of the features you might want to explore are:


  • New Maven extension


  • More functionality in the data control for EJBs (query and range fetching support)


  • New skin for ADF Faces (Fusion skin) which also adds a bunch of animation to things


  • New ADF Faces components - carousel, sparkel graph, autosuggest behavior, emailable pages and more


  • Improvement in the JSF visual editor


  • Better debugger and logging for ADF


  • Bugzilla integration in TPC


  • New features in the database designer
  • UML 2.0 support

And much more.

Download today and start playing...

Join the discussion

Comments ( 3 )
  • horzsolt Wednesday, November 11, 2009
    Hi Shay,
    Thanks the fast information! I've checked the new features, and I'm missing the following items:
    - IE8 support
    - binding support for DVT components
    These are just not included in the release note, or not in the scope of the Jdev11g at all?
    Thanks: Zsotl
  • shay Wednesday, November 11, 2009
    Zsolt,
    IE 8 is supported see:
    http://www.oracle.com/technology/products/jdev/collateral/papers/11/certification/index.html
    I'm not exactly sure what you mean by binding for DVT - the DVT components have been supporting ADF binding for a long time.
    Shay
  • horzsolt Wednesday, November 11, 2009
    Hi Shay,
    Thanks the fast replay!
    Sorry, I wasn't accurate enough when I used the word binding. I mean exactly this:
    http://forums.oracle.com/forums/message.jspa?messageID=3596667#3596667
    Zsolt
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.