I just updated to WildFly 8.0.0.Final-SNAPSHOT including Mojarra 2.2.5 (Mojarra 2.2.5-jbossorg-3 20140128-1641).
Unfortunately, I cannot see any difference. Still, my setText(String s) method is called with an empty string when I leave the field blank.
The only way I currently see is surrounding the setter method with an interceptor method that transforms an empty string to null. But this requires annotating all string setter methods in my bean and shows a significant change in behaviour from JBoss 7.1 to Wildfly which I did not expect.
Any other ideas?
Many thanks and best regards,
do you by any chance have jboss-el.jar in your deployment?
I am afraid not.
What I see in my WEBINF\lib folder:
So the el-Library is obviously taken from the provided JBoss pool, isn't it?
The only thing I changed in the standard WildFly libraries was the adding of the MS SQL driver.
Is there any sensitive standalone.xml configuration that I could have damaged.
Do you have an example .war (with source files) that shows a proper handling of null values?
I had the same problem Dominik, using wildfly-8.1.0.Final and jsf mojarra-1.2_15.
The Strings arrived empty instead of null.
I solved this updating the wildfly EL implementation to javax.el-3.0.1-b05.jar on module org.glassfish.javax.el.
I didn't use javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL property in my web.xml