X

Shay Shmeltzer's Oracle Development Tools Tips

  • March 8, 2006

MVC design pattern applied to documentation

Shay Shmeltzer
Director of Product Management - Oracle

I keep recommending that people who are going to use Oracle ADF in their applications read the new

ADF Developer Guide which is available from OTN. This is your best bet for getting an inside look into how ADF works (along with the SRDemo application).

The problem some people had was that they are going to use ADF Business Components in their application, and currently we only have the Developer Guide that uses TopLink/EJB 3.0. We are working on a version of the developer guide that will use ADF BC - but this is still not out. So some developers are just hanging out waiting for this to come out...

Well I highly recommend that you don't wait and instead start reading the ADF Guide that is out there now. The reason is that this book will teach you about the new ADF binding mechanism, JSF and ADF Faces in very deep details - and this knowledge is applicable to your ADF BC applications as well.

This is the beauty of the ADF MVC based architecture - the way that you develop the View and Controller layer is basically the same regardless of the way you build your Model/Business Services layer.

So go ahead and read this book even if you are going to use ADF BC.

And remeber that you can find a lot of information about ADF Business Components in our 10.1.2 material - basically most of the ADF BC things on the ADF recommended reading page that Steve created will still be relevant to 10.1.3.

Join the discussion

Comments ( 2 )
  • javaX Wednesday, March 8, 2006
    makes sense. this type of architecture / developer info. will help me get up to speed faster. thanks
  • Ariel Wednesday, March 9, 2011
    I'm argentine's. It excuse my english that is not good. Thank by your credits Shay. Very useful. I'm study ADF BC and JDevoloper solutions. Newly, thank.
    Bye.
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.