Why are you doing all those != null checks, rather than displaying them on screen. You need to find where the nulls are coming from.Alternative:Note the %b tag will take foo != null, or foo alone as an argument, displaying "false" from any null reference or false boolean/Boolean and "true" from anything else, including primitives, as far as I can remember.
Dan Acuff wrote:Hi. If my return type for the class is a String.
Will the below be forced on to my web page? I tried it like shown but nothing appeared on my web page.
If the code is in a web application, then no. It will probably go to one of the application server's log files, but exactly which one is server-dependent.
Of course if your question is how to make debugging output appear on the web page, well, you do know how to make text appear on the web page, don't you? Just do that.
Joined: Jul 13, 2009
Thanks for clearing the up! I was starting to get a bit confused.
Yes I can return values to the web-app screen.
The biggest problem I am having is actually reproducing the error. It's like it happens 1 time on a deployment and then it never happens again.
So I am thinking maybe the customerSession was blank or something similar.. but even that does not make sense since you have to be signed in (thereby having a customerSession) before being able to see the detail page where the last 3 reports of it occuring have happened.
It get's tricky when it happens as rarely as it is since I don't know how to reproduce the conditions.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: NullPointerException... what is left to check?