Sunday 14 June 2015

Best Practices for Oracle ADF UI Layer


This blog we will see what are the best practices needs to follow for Oracle ADF UI layer
1. Remove un used an unnecessary code including commented out code.
2. Remove all unused objects and unwanted object creation statements.
3. Remove all unused items from binding page.
4. Should not get the connections explicitly into UI layer and use them(getting connection from data source )
5. Should not call any stored procedures/functions in UI layer by using connection.
6. Add a default activity ID to the welcome-file web.xml.
7. Always reformat code.
8. Ensure compiled(Class files) and temporary files are not checked into source control
9. Define task flow level exception handlers
10. All the managed beans should define in task flows used internally
11. Use isolated data control scope only when required.
12. Always use Data Source instead of JDBC URL in FMW application.
13. Should not call any stored procedures/functions in UI layer by using connection.
14. Ensure all XML files are valid. Use declarative editors for modifying XML over source code
15. Add a default activity ID to the welcome-file web.xml.
16. url.rewriting.enabled should be false in weblogic.xml.
17. Always run jdeveloper Audit facility on your workspace.
18. Don't ignore the warning in jDeveloper.

Thanks..

No comments:

Post a Comment