Changes for page Click to Debug
Last modified by Kieran Kelleher on 2009/08/12 14:33
From version 8.1
edited by Chuck Hill
on 2008/12/17 18:13
on 2008/12/17 18:13
Change comment:
There is no comment for this version
To version 10.1
edited by Chuck Hill
on 2008/12/15 15:27
on 2008/12/15 15:27
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -75,9 +75,7 @@ 75 75 76 76 {{code value="java"}} 77 77 78 -protected void _debugValueForDeclarationNamed(WOComponent component, String verb, String aDeclarationName, 79 - String aDeclarationType, String aBindingName, 80 - String anAssociationDescription, Object aValue) { 78 +protected void _debugValueForDeclarationNamed(WOComponent component, String verb, String aDeclarationName, String aDeclarationType, String aBindingName, String anAssociationDescription, Object aValue) { 81 81 if (aValue instanceof String) { 82 82 StringBuffer stringbuffer = new StringBuffer(((String) aValue).length() + 2); 83 83 stringbuffer.append('"'); ... ... @@ -132,14 +132,12 @@ 132 132 * Little bit better binding debug output than the original. 133 133 */ 134 134 @Override 135 -public void logTakeValueForDeclarationNamed(String aDeclarationName, String aDeclarationType, 136 - String aBindingName, String anAssociationDescription, Object aValue) { 133 +public void logTakeValueForDeclarationNamed(String aDeclarationName, String aDeclarationType, String aBindingName, String anAssociationDescription, Object aValue) { 137 137 WOComponent component = ERXWOContext.currentContext().component(); 138 138 if (component.parent() != null) { 139 139 component = component.parent(); 140 140 } 141 - _debugValueForDeclarationNamed(component, " ==> ", aDeclarationName, 142 - aDeclarationType, aBindingName, anAssociationDescription, aValue); 138 + _debugValueForDeclarationNamed(component, " ==> ", aDeclarationName, aDeclarationType, aBindingName, anAssociationDescription, aValue); 143 143 } 144 144 145 145 /** ... ... @@ -146,14 +146,12 @@ 146 146 * Little bit better binding debug output than the original. 147 147 */ 148 148 @Override 149 -public void logSetValueForDeclarationNamed(String aDeclarationName, String aDeclarationType, 150 - String aBindingName, String anAssociationDescription, Object aValue) { 145 +public void logSetValueForDeclarationNamed(String aDeclarationName, String aDeclarationType, String aBindingName, String anAssociationDescription, Object aValue) { 151 151 WOComponent component = ERXWOContext.currentContext().component(); 152 152 if (component.parent() != null) { 153 153 component = component.parent(); 154 154 } 155 - _debugValueForDeclarationNamed(component, " <== ", aDeclarationName, aDeclarationType, 156 - aBindingName, anAssociationDescription, aValue); 150 + _debugValueForDeclarationNamed(component, " <== ", aDeclarationName, aDeclarationType, aBindingName, anAssociationDescription, aValue); 157 157 } 158 158 159 159 /** ... ... @@ -193,42 +193,6 @@ 193 193 194 194 == Using Click to Debug == 195 195 196 - Run your applicationand look inthe lower, left hand corner. You should see a link like this:190 +Coming soon 197 197 198 -[[image:Click to Open^ClickToOpenLink.png]] 199 - 200 -If you don't, check that the page has the WOLToolBar on it and that the ##er.component.clickToOpen## property is set to true and the ##er.extensions.ERXApplication.developmentMode## property is set to true. 201 - 202 -\\ 203 - 204 -Click on this component to open the Click to Open UI: 205 - 206 -[[image:Click to Open^WOLipsToolbar.png]] 207 - 208 -**EditDisplayAd** is the page in the browser. Click on this link to open this page in Eclipse. 209 - 210 -\\ 211 - 212 -If you are looking for a sub-component of this page, click on the **Click to Debug** link. As you move your mouse over the page, the bread crumb of components will change to show you where you are. Just click to turn binding debug on (or off if it is on) for the component under the mouse in Eclipse. It is that easy 213 - 214 -[[image:ClickToDebugInAction.png]] 215 - 216 -\\ 217 - 218 -With binding debug on, you'll get output like: 219 - 220 -{{code}} 221 - 222 -Dec 13 11:00:29 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage ==> [inline]:HatchEditTask { task=task; } value <com.mdimension.mdtask.model.Task pk:"1027787"> 223 -Dec 13 11:00:29 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage <== [inline]:HatchEditTask { task=task; } value <com.mdimension.mdtask.model.Task pk:"1027787"> 224 -Dec 13 11:00:33 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage ==> [inline]:HatchEditTask { task=task; } value <com.mdimension.mdtask.model.Task pk:"1027787"> 225 -Dec 13 11:00:33 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage <== [inline]:HatchEditTask { task=task; } value <com.mdimension.mdtask.model.Task pk:"1027787"> 226 -Dec 13 11:00:33 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage ==> [inline]:HatchEditTask { task=task; } value <com.mdimension.mdtask.model.Task pk:"1027787"> 227 -Dec 13 11:00:33 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage <== [inline]:HatchEditTask { task=task; } value null 228 -Dec 13 11:00:33 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage ==> [inline]:HatchEditTask { task=task; } value null 229 -Dec 13 11:00:33 MDTask[62934] (ERXNSLogLog4jBridge.java:46) DEBUG NSLog - HatchViewTaskPage <== [inline]:HatchEditTask { task=task; } value null 230 - 231 -{{/code}} 232 - 233 -So what that's showing is HatchViewTaskPage component is pushing the task binding into the HatchEditTask component with the value Task 234 -1027787, then HatchEditTask component is pushing the binding back up. So you can see here that 6th line, HatchEditTask component is pushing a null binding back out (which, in this case, was causing a problem I was trying to find). 192 +== ==