Oracle JDeveloperOracle ADF 11g Production Project Experience
Oracle JDeveloperOracle ADF 11g Production Project Experience
Andrejus Baranovskis Independent Oracle Consultant Red Samurai Consulting Oracle ACE Director
Oracle Develop, Oracle OpenWorld 2009
Outline
Project Reference Sample Development Time Estimation Development Best Practices Quality Extension Team Development Lessons Learned Contacts
"Oracle ADF 11g was the natural choice for us and we believe that it will help us upgrade our technology platform too while maintaining most of the rich UI features of Oracle Forms."
- Gerry Raftopoulos, General Manager, MedNet International Ltd.
ADF Faces Rich Client ADF Task Flows ADF Business Components
Oracle WebLogic Server 11g R1 Oracle Application Server 10g R2 Oracle Reports 10g R2 Oracle RDBMS 10g R2
Project Manager Technical Manager Technical Consultant 16 Oracle ADF Developers 200 Forms to develop 27 Logical Modules developed already 2600 ADF Business Components elements developed already 300 Java classes developed already 240 Web Pages developed already
MedNeXt - Authorisation
MedNeXt - Authorisation
MedNeXt - Incident
MedNeXt - Claim
MedNeXt - Invoice
Estimated time: 296 hours Actual development time: 290 hours Model: 1 Application Module, 12 View Objects, 52 Entity Objects, 35 LOV, 10 View Links, Inheritance ViewController: 3 ADF Task Flows, 5 ADF Regions, complex CRUD functionality, 9 Data Blocks
Complexity:
Complexity:
Model: 1 Application Module, 1 View Object, 25 Entity Objects, 20 LOV ViewController: 2 Query Criteria, Result Table, Export to Excel functionality, Integration with Event Maintenance form
Application Structure and Packaging Reusability Oracle ADF Tuning Application Splitting and Integration Forms to Fusion Modernization
Model
Common Model: Entity Objects and LOV View Objects Form Specific: Application Module and View Objects
View-Controller
Model Reusability
ViewController Reusability
JSF Fragments
One Application:
Complex to Monitor and Control Development JDeveloper Performance Overload Improves Development Performance Complex to Maintain ADF Libraries ADF Task Flows
Splitted Application:
ADF Libraries
Lessons Learned:
Never call Application Module from ViewController directly Extract common files to separate project and reference it through dependency From the beginning maintain proper application structure suitable for splitting In JDeveloper 11g R1, jazn-data.xml can't be reused Assign different Managed Bean names Try to avoid circle dependency
Validation execution CRUD operations for Master-Details Default Form opening and navigations
Be careful with PL/SQL usage in J2EE architecture Consider performance differences between Web and Client-Server applications Consider Automatic generation VS. Development approach
Development Team
JDeveloper 11g MedNeXt Quality Extension Cross-check code reviews, JDeveloper 11g Show Overview Code reviews during SVN merges Automatic Builds, Code Quality reports No JUnit Manual Test Cases execution Test Cases are based on Development Specifications
Test Team
JDeveloper 11g R1 extension is developed based on ADF development rules violations collected during manual Quality Reviews Provides automatic Quality Review for Model and ViewController Performs automatic scan on Package level
Entity Attribute Label Missing LOV Primary Key Missing View Object Order By Clause Bind Variable Set to Hidden Overridden Class Check
Table Parent Panel Collection Task Flow Return Exist Missing Backing Bean in Request Scope Task Flows is From Main Task Flows Parameter Starts with In
Team Development
Complex to control concurrent changes in ADF metadata files Frequent runtime errors due to corruptions in ADF metadata files No stable branch at any point of time Easier to maintain Separate SVN branch is created for each logical module Development bugs in SVN branch are not blocking other modules development Always stable Trunk branch Complex to maintain
Oracle Develop, Oracle OpenWorld 2009
Team Development
SVN Branches Merging is supported in JDeveloper 11g Developers should update their SVN branches only with critical patches from trunk Before commiting merged development branch into trunk, changes should be reviewed
Lessons Learned
Define reusable application structure from the beginning Split development into multiple applications and integrate into one Implement automatic builds procedure Be careful with PL/SQL usage in JEE systems Use standard ADF functionality, avoid custom solutions. Centralize custom code in extension classes Design and Test UI behavior properly before development Cross-check development quality Use SVN branches for different modules and maintain them Train developers for at least 1 month Be ready to prove new design to Form users
Contacts
Questions
Answers