Debugging ADF Apllication
- How to Enable ADF Business Components Debug Diagnostics
open the Run/Debug/Profile page in the Project Properties dialog for your data model project. Click Edit to edit the chosen run configuration, and add following string to the Java Options field in the page.
-Djbo.debugoutput=console
Example:
Diagnostic Output of Business Component Browser: [355] Oracle SQLBuilder: Registered driver: oracle.jdbc.OracleDriver [356] Creating a new pool resource [357] **** DBTransactionImpl establishNewConnection [358] Successfully logged in [359] JDBCDriverVersion: 11.1.0.7.0-Production [360] DatabaseProductName: Oracle [361] DBTransactionImpl initTransaction [362] Replacing: null with: StoreServiceAM_AddressesPageDef [363] Replacing: null with: StoreServiceAM_MostPopularProductsByCategoriesPageDef ... [537] Orders ViewRowSetImpl.execute caused params to be "un"changed [538] Column count: 41 [539] ViewObject: Orders Created new QUERY statement [540] Orders>#q computed SQLStmtBufLen: 952, actual=865, storing=895 [541] SELECT OrderEO.ORDER_ID, OrderEO.ORDER_DATE, OrderEO.ORDER_SHIPPED_DATE, FROM ORDERS OrderEO ORDER BY OrderEO.ORDER_DATE desc [542] Bind params for ViewObject: Orders
Another Effective way to debug all SQL and DML statemnts occurs on your application is to set oracle.jbo.common.ADFLoggerDiagnosticImpl to FINEST
To do this follow these steps
1- Run or debug you application
2-From window menu>select Application server
3-Right click on Integrated weblogic server and select configure oracle disgnosics
4-expand the tree oraclejbo , you will not Find oracle.jbo.common.ADFLoggerDiagnosticImpl so you have tto add it
5- to add it click om add button above and write oracle.jbo.common.ADFLoggerDiagnosticImpl to search it and add it
NOW YOU CAN SEE THE qUERY AND dml STATMENTS IN YOU LOG PAN
ENJOY
Comments