Quick Tips for Oracle ADF 12c Certified Implementation Specialist (1Z0-419) Exam

I passed the ADF 12c Implementation Specialist Exam last month. Lot of people had queries on the pattern/study material etc., so thought to write a quick blog -

• The study material is same as Oracle ADF 11g Exam [D57350, D60499, D60501] though exam is much tougher than ADF 11g (I have cleared ADF 11g earlier as well)
• No new features or concepts in ADF 12c have been covered in the exam
• This is the best Oracle Exam I have given, totally conceptual, cringes you for time and challenges your concepts
• 87 questions in 120 mins with multiple choice questions, I took the entire time.
• Quite a few questions require you to choose the best option from all the right options :)
• Few questions have screenshots and questions are asked pertaining to them which I though was a great idea to check implementation experience
• If you have cleared the ADF 11g exam in the past and have got implementation experience, just a revision of the ADF 11g material should be good enough.
• Do not attempt this exam without having hands on in ADF, it's pointless :)
• Be very thorough on the ADF Lifecycle and ActionListener/ValueChangeListener order of execution, Nested AMs and transaction, DVT components, page templates, ADF BC; quite a few questions from there ! [D60501 is the guide to read for these]

Kudos to the certification team for such a comprehensive exam, I felt really happy on having cleared it !!

Useful links -
Exam Details and Topics (Cover all topics, questions from each are asked)
Study Guide details

ADF : Refactoring/Modularizing your AMImpl code

Lot of our ADF Applications use a single Application Module(AM henceforth) to house most of the business logic. Thus results in a huge AMImpl.java which keeps growing and eventually becomes difficult to maintain with multiple developers working on it.

With this file being the heart and soul of the application , it would not hurt to refactor the business logic within it to separate standalone Java classes which can be separated out based on some functional/logical separation.

This can be easily achieved by calling these standalone Java classes from the AMImpl.java and passing the AM instance to them so that the required operation could be carried out independantly and in context.The AMImpl.java just houses the skeleton methods to call the standalone Java class methods.

Example

Code in <yourAMName>Impl.java

       public void scheduleJobViaAM(){ // this could be called from the UI via method call in a Taskflow

        Scheduler scheduler=new Scheduler(); // can be made a static class as well based on need

        scheduler.scheduleJobsViaQuartz(this);

    }

Code in StandAlone java class

    public void scheduleJobsViaQuartz(ApplicationModuleImpl am){// accepts an instance of super Class of our AMImpl.java'

         OrgAMImpl orgAM=(OrgAMImpl)am; //typecast AM  to its appropriate Impl class to get access to its method and objects

        orgAM.commitSalaryForEmployee(100); // call AM method to do processing with its VO Instances , alternatively that code could be written here too since we have a handle to the AM instance !

 }

Finally we have more readable , manageable code which goes a huge way in having a timely delivered project with minimum issues  !