Developer & Development Time basically get reduces if you are using Debugger WLS,
Here we go,
1.System.out.println - Newbie will use s.o.p each and every statement. so what's going on.
2.Avoid Re-run. - For a Small Change in Java Class(Application Module/EO/VO/Bean). No Need to Run Entire Application.
3.Bug Findings - Easy error findings.
Various Options for Debugging:
Option 1: By using this statement "-Djbo.debugoutput=console" in Model Layer. you can see SQL query being sent to server in your console log.
Note : If you are going to use this option means, After pressing OK button. need to restart your server.
Option 2: Have a break point (by pressing 'F5') in your java code.then start debugger along with your application.
While Performing Selection/Action. By pressing F8(Step by step execution on code)
By pressing F9(Navigate to Next Break point). Blue Color shows Execution Point.
After execution of a row. you can mouse over on the particular class for see the values.
say as e.g.: After execution row class. I can able to see a entire row what i selected in page.
Options 2.1: By using "EL Evaluator" you can debug. With the help of El expression i can able to get the row count.
Options 2.2: By this "Smart Data" you can debug Model and its values (say as e.g.: debug the queries)
Options 2.3: By this "Data" you can debug the Bean and its values.
Options 2.4 : By this "ADF Data" you can debug the Various Scope and its values
Request Scope: Bindings Flows out on this scope.
View Scope: PageDef Flows out on this scope.
Session Scope: Active Data Services Flows on this scope.
Application Scope: Application name and its location flows on this scope.
While debugging,
In Browser: Few couple of things can able be noticed
In Application Data: Entire db data can able to see here
By this way you see the state of Enity Object and its Data.
In Jspx Page: By this way you see the entire value and expersion of an Page.
Option 3: Configuring Diagnostic Logging.
Tune into Finest Level.
These are the various kind of Debugging.
Debugging Part 2 & 3(LifeCycle Level) in future posts.
Here we go,
1.System.out.println - Newbie will use s.o.p each and every statement. so what's going on.
2.Avoid Re-run. - For a Small Change in Java Class(Application Module/EO/VO/Bean). No Need to Run Entire Application.
3.Bug Findings - Easy error findings.
Various Options for Debugging:
Option 1: By using this statement "-Djbo.debugoutput=console" in Model Layer. you can see SQL query being sent to server in your console log.
Note : If you are going to use this option means, After pressing OK button. need to restart your server.
Option 2: Have a break point (by pressing 'F5') in your java code.then start debugger along with your application.
While Performing Selection/Action. By pressing F8(Step by step execution on code)
By pressing F9(Navigate to Next Break point). Blue Color shows Execution Point.
After execution of a row. you can mouse over on the particular class for see the values.
say as e.g.: After execution row class. I can able to see a entire row what i selected in page.
Options 2.1: By using "EL Evaluator" you can debug. With the help of El expression i can able to get the row count.
Options 2.2: By this "Smart Data" you can debug Model and its values (say as e.g.: debug the queries)
Options 2.3: By this "Data" you can debug the Bean and its values.
Options 2.4 : By this "ADF Data" you can debug the Various Scope and its values
Request Scope: Bindings Flows out on this scope.
View Scope: PageDef Flows out on this scope.
Session Scope: Active Data Services Flows on this scope.
Application Scope: Application name and its location flows on this scope.
While debugging,
In Browser: Few couple of things can able be noticed
In Application Data: Entire db data can able to see here
By this way you see the state of Enity Object and its Data.
In Jspx Page: By this way you see the entire value and expersion of an Page.
Option 3: Configuring Diagnostic Logging.
Tune into Finest Level.
These are the various kind of Debugging.
Debugging Part 2 & 3(LifeCycle Level) in future posts.
No comments:
Post a Comment