RE: Tomcat8 coercing behavior

2014-10-15 Thread Koen Serneels
MT+03:00 Koen Serneels : > > Hi, > > > > When binding a JSF input text to a String property of a JSF > ManagedBean, I want that an empty value is mapped to null and not "" (empty > string). > > So, on tomcat7 (7.0.56) with JSF(2.2) I can get this to work n

Tomcat8 coercing behavior

2014-10-15 Thread Koen Serneels
Hi, When binding a JSF input text to a String property of a JSF ManagedBean, I want that an empty value is mapped to null and not "" (empty string). So, on tomcat7 (7.0.56) with JSF(2.2) I can get this to work nicely by controlling the coercing behavior with the JVM property org.apache.el.pars

Registering Filters via API: isMatchAfter behaves weird

2012-04-04 Thread Koen Serneels
Hello, I came across weird behavior using the JEE Servlet 3.0 API for adding Filters with Tomcat 7.0.26 When I map two filters on the same URL and I use the "isMatchAfter" attribute I would expect the filter having "isMatchAfter set to true to be invoked last. For example: FilterRegistrati