One of the old JHeadstart blog posts (of the orablogs site) that is still valid, is the one about ADF BC Diagnostics. It mentions jbo.debugoutput, jbo.logging.show.function, and jbo.logging.show.timing. It also explains how to interpret the timing.
See also the ADF Developer's Guide for Forms/4GL Developers, section 5.5.3.2 Enabling ADF Business Components Debug Diagnostics.
« Speeding Up JDeveloper 10.1.3 | Main | Deploying JHeadstart applications to OC4J 10.1.3.2 or higher »
ADF BC Diagnostics
Search All Blogs
Google Search
About This Entry
This page contains a single entry from the blog posted on November 26, 2007 11:07 AM.
The previous post in this blog was Speeding Up JDeveloper 10.1.3.
The next post in this blog is Deploying JHeadstart applications to OC4J 10.1.3.2 or higher.
Many more can be found on the main index page or by looking through the archives.
Top Tags
- ADF
- ADF BC
- ADF Controller
- ADF Faces
- ADF JHeadstart Workshop
- bounded task flows
- business rules
- custom templates
- debugging
- declarative validation rules
- dynamic regions
- Expression Language
- Forms
- Forms Migration
- Forms2ADF Generator
- JDeveloper
- JHeadstart
- JSF
- LOV
- OO principles
- OOW
- page fragments
- page templates
- query operator
- REA
- search
- shell page
- stand-alone pages
- static regions
- unbounded task flows
- WebCenter
- Working Sets
- XML menu model
Comments (1)
What a coincidence .. I also used that article yesterday :-) Thanks for sharing!
Posted by Koen Verhulst | November 27, 2007 12:53 AM