Win a copy of The Java Performance Companion this week in the Performance forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

Confusion in EL

 
chou hung
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi,

Given the code as below:



The result is true.

Since EL treats null object as false in logical expression and map.c actually exists, does anyone have idea why the result is true?
 
Dee Brown
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I believe it is because ${requestScope.map.c} returns "42". Since "42".equalsIgnoreCase("true") == false, ${not requestScope.map.c} == true.
 
chou hung
Greenhorn
Posts: 2
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Dee,

Thanks for the reply. That makes sense.
 
sudhakar karnati
Ranch Hand
Posts: 93
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I believe it is because ${requestScope.map.c} returns "42". Since "42".equalsIgnoreCase("true") == false, ${not requestScope.map.c} == true.


Sorry i could not understand the explanation above(in Bold)..if i had missed any topic related to this in HFSJ please tell me the page number so that i can go back and read once again..

Thanks & Regards,
Sudhakar Karnati
 
Dee Brown
Ranch Hand
Posts: 94
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In the statement, "${not requestScope.map.c}", the "not" operator coerces the evaluation of "requestScope.map.c" (i.e. "42") to a boolean. In simple terms, a boolean X is true when X.equalsIgnoreCase("true") is true. Therefore, since
"42".equalsIgnoreCase("true") == false, its negation (i.e. ${not requestScope.map.c}) is true.
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic