You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Andreas Hartmann-Schneevoigt (JIRA)" <de...@myfaces.apache.org> on 2009/03/15 17:52:50 UTC

[jira] Commented: (MYFACES-1979) -Values from View converted to standard-values using tomcat 6.0.16 or 6.0.18

    [ https://issues.apache.org/jira/browse/MYFACES-1979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12682159#action_12682159 ] 

Andreas Hartmann-Schneevoigt commented on MYFACES-1979:
-------------------------------------------------------

Hi there,

is its possible to give a workaround by solving https://issues.apache.org/jira/browse/MYFACES-1902 ? It may be enough to change the EL Implementation to work around this issue which is really a strong behaviour.

I cant imagine a case where a generic default value is that what the developer really wanted ... but this must be addressed to the jsp spec ...


> <null>-Values from View converted to standard-values using tomcat 6.0.16 or 6.0.18
> ----------------------------------------------------------------------------------
>
>                 Key: MYFACES-1979
>                 URL: https://issues.apache.org/jira/browse/MYFACES-1979
>             Project: MyFaces Core
>          Issue Type: Bug
>    Affects Versions: 1.2.4
>         Environment: myfaces core 1.2.4, tomahawk 1.1.7, sandbox 1.1.7, tomcat 6.0.16 or 6.0.18
>            Reporter: Martin Winkler
>
> Hi there,
> Using tomcat 6.0.16 or 6.0.18 there seems to be a bug with myfaces (currently using 1.2.4, but had the bug with 1.2.2, too).
> If I leave Input-Fields empty, the model is updatet with default-values (e.g. "0" for a Long-variable or a zero-length String for a String-variable) for the corresponding variables instead of <null>-Values. I think the bug is not located in converters.
> Found some information here:
> http://www.icefaces.org/JForum/posts/list/8024.page
> It would be good to use tomcat 6.0.18 because in older versions there is a security issue. With tomcat 6.0.14 everythiing is allright ..
> Thanks,
> Martin

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.