Académique Documents
Professionnel Documents
Culture Documents
ESolution Software
2) NEVER change your UI layout properties in processFormRequest().
ALWAYS make changes in processRequest(), even if that means handling
an event in processFormRequest() and then redirecting back to the same Blogs I Like
page. This ensures that the web bean hierarchy is in a stable state when the
Gizmodo
page renders.
Steven Chan
3) NEVER use index numbers to find beans when you want to change their Tom Kyte
5) NEVER instantiate Beans using "new OA*Bean()". ALWAYS use the OA Framework or ADF?
createWebBean() factory methods available on the OAControllerImpl class. OAF Key Do's and Don'ts
Not all Bean properties are initialized correctly when you use "new." (Part 1) - "Top 10"
Golden...
6) NEVER create Form Beans in code (this means NEVER add nested ► March (3)
Form beans to a page; your Page Layout region should be the only form
region). Multiple form Beans on a page are not supported and can result in ► 2006 (10)
strange runtime behaviors.
http://andrieshanekom.blogspot.com/2007_06_01_archive.html 19-09-2010
The Oracle EBS Developer: June 2007 Page 2 of 3
8) NEVER use JDBC directly unless you're calling a PL/SQL routine (you
should use a view object instead, and if possible, the view object should be
defined declaratively and not programmatically).
Picture Window template by Josh Peterson. Template images by mariusFM77. Powered by Blogger.
http://andrieshanekom.blogspot.com/2007_06_01_archive.html 19-09-2010
The Oracle EBS Developer: June 2007 Page 3 of 3
http://andrieshanekom.blogspot.com/2007_06_01_archive.html 19-09-2010