Solarbox - Troubleshooting

JWAD >

Why don't I see the JWAD debugger console on the page?

There are two reasons why this might happen. Either the JWAD custom tag include is not included on that specific page or the "jwadEnabled" context parameter specified in the deployment descriptor is set to false.

Why doesn't the JWAD debugger console appear exactly where I placed it in my JSF page?

Most likely, JavaServer Faces is throwing the console outside the component tree because it's not wrapped as a JSF component. To fix it, simply wrap the JWAD debugger console in JSF "verbatim" tags.

<f:verbatim>
	<jwad:debugger />
</f:verbatim>

Why do I only see the class name and hashcode for a displayed value (for example, com.solarbox.Example@12345)?

Under the hood, when JWAD encounters an object, it calls that object's toString() method. Therefore, objects will only display meaningful information if their toString() method has been properly overridden.

To get the most out of JWAD be sure to override every object's toString() method placed into a scope. When you think about it, that's what the toString() method was intended for - debugging purposes.

As a best practice, I strongly recommend using the commons-lang API provided by the Apache Software Foundation for overriding your toString() methods. The advantage is that it's only one line of code and it automatically keeps your method up-to-date. You don't have to worry about updating your toString() methods as you add and remove attributes from your objects because that one line of code uses reflection to dynamically print those attributes when invoked.

Why can't I see the cookie I just created?

Try refreshing the page. Remember that cookies are added to the response, so you may simply be one refresh behind. JWAD will pick up the freshly baked cookie on the next request.