Article:		JSP 2.0: The New Deal, Part 1
Subject:		EL - I just don't get it!
Date:		2003-11-11 10:55:12
From:		anonymous2
Response to: EL - I just don't get it!
Chalk up one more person that just doesn't get it. One more language makes no sense to me.

Showing messages 1 through 4 of 4.

• EL - I just don't get it!
  2003-11-13 18:20:51  dhinojosa [View]
  
  
  The other value, is object reference navigation where you didn't have that before. To me that is the most valuable aspect of JSTL.
  
  For example
  <c:out value="${employee.address.zipCode}"/>
  <c:out value="${employee.401k.provider.address.zipCode}"/>
  
  This is far better than <jsp:getProperty> as you can only inspect only one level deep.
  
• but why is its failure mode so unusable
  2003-11-15 22:59:51  anonymous2 [View]
  
  
  I used the JSTL stuff last year, and ended up hating that expression language for the bugs it gave me that took ages to track down.
  
  EL says 'if something evals to null, the statement evaluates to empty'. Typos turn expressions to null. Errors in your java code where things are initialized and return null, turn expressions to null. Which makes it really hard to track down where is the error in employee.401k.provider.address.zipCode
  
  For all the expressiveness of the language, if it is hard to develop working code, I dont see the point.
  
  -steve loughran
• but why is its failure mode so unusable
  2003-11-29 22:52:16  anonymous2 [View]
  
  
  In an MVC environment you can see what evaluates to null in a servlet before rendering to JSP.

• EL - I just don't get it!
  2003-11-12 07:51:50  anonymous2 [View]
  
  
  OK, replying to myself, I've reread this article and it makes a little more sense and makes EL look a little more useful and a little less like one more new thing to learn in order to continue writing JSPs.
  
  Still I do wonder about all the compications that have been added to JSP in order to simplify it.