Best of Both Worlds with ADF

I’m seeing a lot of interest in developing client-side applications based on one JavaScript framework or another. Today, the leading contenders are AngularJS (the old version) and Angular2 (the new version, of course, incompatible with the old). Oracle is also entering the game with Oracle JET.

For some strange reason, developers tend to compare Javascript frameworks to full stack frameworks like ADF, forgetting that someone, somewhere, must build the REST web services that JavaScript applications are based on.

ADF to the Rescue

In most JavaScript client projects I see, the REST services are built in plain Java turned into web services with JAX-RS annotations. For an ADF developer, this is obviously a wasteful way to build services, re-inventing lots of things that already exist in ADF (declarative validations, master-detail coordination, and many other things).

Fortunately, with ADF 12.2, we can now publish our ADF view object instances as REST web services. It is well described in the manual, and there is also a blog post with video by Shay Shmeltzer showing how it’s done.

As an ADF developer today, you definitely need to be able to publish your view objects as REST services. In this way, you can build most of the functionality fast with the power of ADF faces, and the small part of the application it might make sense to build in JavaScript can use the same business logic.


This post originally appeared in the monthly ADF Mastery newsletter. Don’t miss the next one, sign up here.