|Re: JSPs throwing incorrect compiler warnings [message #505421 is a reply to message #505407]
||Wed, 30 December 2009 13:24
| David Kerber
Registered: July 2009
In article <firstname.lastname@example.org>, wknauf_NO_@_INSIDE_hg-|
> Hi David,
> I think I see the reason: your JSP validation settings are not the default ones,
> and you switched some from "ignore" to "warning".
> The settings are (either project specific through "Properties" => "Validation"
> or global through "Preferences" => "Web" => "JSP files" => "Validation"): Group
> "Java", options "Null pointer access" and "Unused import".
> By default, the full group "Java" is set to "Ignore".
But I want it to check MY code in a .jsp, just not the generated, so I
don't want to turn off jsp checking.
Even with that, why does it think "Session" can only be null at some
point? It obviously cannot be null in a jsp, so why does it think it
is? Sounds like a true bug in null checker, wrt .jsp files.
> But it does not make sense that those errors appear. So, maybe someone
> conceptual knowledge of validation can comment on this.
Yes, that is the root of my question.
Powered by FUDForum
. Page generated in 0.03544 seconds