DevGrok

I recently came across a problem where I was expecting a null value to be populated into one of my JSF managed beans on submit. After digging through the entire stack, I found out this was deliberate. This bug was introduced into Tomcat 6.0.16, as a consequence of implementing the EL spec to the letter. The option to disable this change at command line was added in 6.0.17: -Dorg.apache.el.parser.COERCE_TO_ZERO=false A patch in Tomcat 6.0.24  was added to allow you to change it at run time: System.getProperties().put("org.apache.el.parser.COERCE_TO_ZERO", "false"); This problem also directly occurs in JSF, as it uses an EL engine as well. There's a  patch for 1.2_08-b01  but it is happening in 2.0.2. But the above fix seems to work. Request to change the JSP Spec As per chapter 1.18.2 and 1.18.3 of EL spec, EL coerces null values to non-null values such as empty String or (Long) 0 or (Boolean) false. This behaviour is in almost all cases unwanted when t

Previously I have been using GuiceSF to inject the JSF managed beans which extends the Mojarra's implementation of ELResolver ( ManagedBeanELResolver ). This was bit of a hack but it was relatively simple to implement. In upgrading to newer version of JSF, I had to manually tweak it to keep it in line with the new features in the spec which took a fair amount of debug stepping. So when JSF 2 came out I looked around for a way to do it which still used the implementation's bean creation and handling but also injected it with Guice. After digging around in the injection code in Mojarra, I saw how simple it would be to extend the provided Tomcat injection (which injects stuff for the @Resource and @EJB etc annotations). This solution first requires the injection provider be specified in web.xml: <context-param> <description>JSF Injection provider</description> <param-name>com.sun.faces.injectionProvider</param-name> <param-value>