Oracle ADF support on JSF 2.3

Skip to first unread message

Jeba Jothimoni

Jan 3, 2019, 3:29:44 PM1/3/19
to ADF Enterprise Methodology Group



Recently came across this presentation slide.

I really like how the presenter explained the content.


On slide 33, the content goes like this:

Oracle ADF is based on JavaServer Faces. You love it or hate it. There is not middle point.
Oracle ADF (latest release) is based on JSF 2.2. There are not plans for upgrading Oracle ADF to be aligned with JSF 2.3+ and beyond. Oracle ADF is still supported by Oracle, but it will not receive major improvements or upgrades.

He still recommends using ADF, if you follow through this entire presentation.


Is this officially true that Oracle will not support JSF 2.3+ in Oracle ADF? Can anyone confirm or update on this statement?

He also explained how we can work around those new features of JSF 2.3 within ADF. But that’s not the clean way for a mature and established enterprise technology like ADF Faces. Then we will recreate or work around any new features of JSF within ADF.


Jeba Jothimoni,

Oracle Certified Master Enterprise Architect, PMP®, PMI-ACP®

Senior Solutions Architect, Aires

Tel +1.412.788.0461 • Direct +1.412.677.1693

website • email • connect on LinkedIn


Nyemike Onukwu

Jan 4, 2019, 12:57:02 PM1/4/19
This is interesting information. can someone confirm what Jeba is asking about the future of adf ?

Jeba a while ago. Someone on this group shared information about an Oracle adf 19

see below:

I have had to look at this document again and no mention of an upgrade to jsf 2.3. What is mentioned is 100 adf faces enhancements. 

So I guess the author of the slides you shared is right. No plans to upgrade to jsf 2.3 and beyond. 

It will be nice if an authority from Oracle sheds more light on this. I just recently started using Oracle adf for my software project the future of the framework is key to me.

You received this message because you are subscribed to the ADF Enterprise Methodology Group ( To unsubscribe send email to
All content to the ADF EMG lies under the Creative Commons Attribution 3.0 Unported License ( Any content sourced must be attributed back to the ADF EMG with a link to the Google Group (

You received this message because you are subscribed to the Google Groups "ADF Enterprise Methodology Group" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
For more options, visit

Shay Shmeltzer

Jan 7, 2019, 12:27:37 PM1/7/19
The first release of ADF 19 is planned to still be using the same Java EE and JDK editions - so no transition to JSF 2.3.
However - there is always a chance that future versions beyond that will adopt newer Java EE editions.


Shay Shmeltzer
Director of Product Management, Oracle Cloud Development Tools

Jean-Marc Desvaux

Jan 7, 2019, 1:54:20 PM1/7/19
Thanks Shay.

"There is always a chance...." means a lot I think.

Sorry for the sarcasm but it looks like 
ADF is nearly dead ... and may die even before Forms...



Jan 15, 2019, 11:04:01 PM1/15/19

Hi Shay,


Thanks for the response. 


Looks like ADF 19 feature additions are primarily to make the ADF applications Cloud compatible or paving the road to move the ADF application to Oracle Cloud. 


“There is always a chance…” is suggest me to second/accept Jean-Marc's comment. 

Should we start planning on migrating ADF to another technology?


Any comments or suggestions from Chris, Frank and other ADF experts/promoters?

Jan 16, 2019, 12:27:23 PM1/16/19
Jeba / Jean-Marc,

Do you guys know of any successful implementation of Oracle JET (or similar JS techs such as AngularJS) as front-end for BPM human tasks, replacing ADF? 
Is this something any of you are considering, assuming this bleak picture of ADF's future?

Rodrigo Vrindavan

Shay Shmeltzer

Jan 16, 2019, 12:44:00 PM1/16/19
ADF is already cloud compatible. You can easily deploy your ADF apps to the Oracle Java Cloud Service without requiring changes to the app.
(both and 12.2. versions). This is not new - here is a blog from 2013 that showed how to do it:
And there are many other blogs covering this - for example:

As for “Should we start planning on migrating ADF to another technology?” 
If ADF answers your technical requirements and you are happy with the solution it provides (both design time and runtime) then there is no reason to move away from ADF. 


Shay Shmeltzer
Director of Product Management, Oracle Cloud Development Tools

Carlos Marques

Jan 16, 2019, 5:11:59 PM1/16/19
Both ADF and JET are viable solutions but if the existing conditions allow us to pick one or the other, then Oracle JET is the way to go. 

For the organizations that already have ADF then the usual "if it's working don't fix it" apply. BUT if the organization is adding more functionality to it then depends of a lot of things (NFR, the organization, business product roadmap and legacy systems). It's usually a obvious call to make when you have all the data but sometimes a less black or white solution may be the way to go. Namely a hybrid approach.

Regarding the question of using Oracle JET with Oracle BPM it's as easy as using ADF, Sharepoint or anything else on top of Oracle BPM. We have projects with the specific case (Oracle JET+Oracle BPM) and it works as expected. 

Carlos Marques


Tshifhiwa Madima

Jan 16, 2019, 5:14:45 PM1/16/19

Alejandro Tovar Lanz

Jan 17, 2019, 11:05:45 AM1/17/19
Just FYI - attended Oracle Open World Europe in London - ADF nowhere to be seen ☺ not even a 15 minute session. 

Again, just FYI. 

Alejandro Tovar Lanz

       Oracle Webcenter & ADF 
          Consultant | Director
       M: +44 7539048598


this is to avoid signature trimming. Please ignore.

Amr Gawish

Jan 17, 2019, 12:43:48 PM1/17/19
I've been watching this thread for a couple of weeks now, and I want to share my thoughts, and hopefully no one would be offended as developers/consultants/engineers/etc... can be quite religious about their choice of framework/technology forgetting that it is just a tool to help you solve a problem faster, and changing that tool is part of progress.

ADF is not trendy/popular right now because of two big reasons in my opinion:

1. It is tightly coupled with an IDE (JDeveloper)*. That means two teams - or more! - need to work to make such an update, and if there are no updates to JDeveloper, then ADF is not progressing.

2. ADF is not architectured to work as a MicroService or in a standalone Jar file. With the movement to microservice and containers and more DevOps oriented pipelines, ADF still uses Weblogic (JEE) which doesn't adhere to Microservice architecture. JEE is also in a weird place right now with Eclipse taking charge and taking its time to decide what to do. Unless the next ADF version can work as a Microservice - maybe by making ADF Faces optional or making REST-first approach - on its own, it wouldn't be able to compete**.

There are multiple other reasons like ADF not utilising more Java 8+ functional features, or Java 9+ modular features, and other bits and pieces that made me move away from ADF. I do believe however that the above two reasons are my main reasons, and if you're starting a new project I don't think ADF should not be in your choice list given that it would be a very steep learning curve for young developers and there are a lot of other options out there!

* I know there is a plugin for Eclipse, but Eclipse usually comes second in term of new features after JDeveloper!
** I also know that there are ways to make ADF applications work in containers and in a Microservice fashion, but ADF was not architectured for that, and there are more natural ways to do with other frameworks.

Best Regards,

Reply all
Reply to author
0 new messages