It still is buggy, a friend of mine ran into issues with the latest
tomcat 7 afair, and as soon as he replaced it with juel after my advice
the issues were gone.
Werner
Am 10.01.11 17:22, schrieb Mark Struberg:
nope, I found the tomcat 7 EL to be buggy back when I did need it (should
re-evaluate it soon) and use juel now [1]
LieGrue,
strub
[1] https://github.com/struberg/juel
--- On Mon, 1/10/11, Marsman<mars....@gmx.de> wrote:
From: Marsman<mars....@gmx.de>
Subject: Re: How to persist null values with JSF2?
To: users@myfaces.apache.org
Date: Monday, January 10, 2011, 2:59 PM
After googling another 2 hours I found the solution: Since
tomcat 6.0.16 we
have to add the org.apache.el.parser.COERCE_TO_ZERO=false
VM argument.
@Strub: Did you have set this VM argument too?
For more infos:
http://balusc.blogspot.com/2008/07/dao-tutorial-use-in-jsf.html#EmptyToNullConverter
EmptyToNullConverter
struberg wrote:
Hmm, works perfectly over here when adding the
following to web.xml:
<context-param>
<param-name>javax.faces.INTERPRET_EMPTY_STRING_SUBMITTED_VALUES_AS_NULL</param-name>
<param-value>true</param-value>
</context-param>
as Jakob already suggested.
LieGrue,
strub
--- On Mon, 1/10/11, Marsman<mars....@gmx.de>
wrote:
From: Marsman<mars....@gmx.de>
Subject: Re: How to persist null values with
JSF2?
To: users@myfaces.apache.org
Date: Monday, January 10, 2011, 1:52 PM
The action on the commandButton calls a
save()-Method in my
backing bean. At
this point, I got the empty fields instead of
null. You can
see this in my
initial post. I'm using JPA with Hibernate.
Titus
struberg wrote:
Did you do your debugging in your backing
bean action
or do you only look
at the database? If JPA is involved, then the
jpa
provider may replace
null with empty strings (known issue on
oracle).
LieGrue,
strub
--- On Mon, 1/10/11, Marsman<mars....@gmx.de>
wrote:
--
View this message in context:
http://old.nabble.com/How-to-persist-null-values-with-JSF2--tp30622750p30634470.html
Sent from the MyFaces - Users mailing list archive at
Nabble.com.
