You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@tapestry.apache.org by "Radek Terber (JIRA)" <ji...@apache.org> on 2013/09/19 14:34:51 UTC

[jira] [Created] (TAP5-2186) Null Boolean values passed from component to the variable are changed to "false"

Radek Terber created TAP5-2186:
----------------------------------

             Summary: Null Boolean values passed from component to the variable are changed to "false"
                 Key: TAP5-2186
                 URL: https://issues.apache.org/jira/browse/TAP5-2186
             Project: Tapestry 5
          Issue Type: Bug
          Components: tapestry-core
            Reporter: Radek Terber


We have component that contains Boolean (= object) variable annotated as @Parameter - it is designed to be passed on this component from outside and should return the Boolean value to the caller.

When we set null value for this variable, the caller gets "false". I was not able to pass null value to the caller any way.

I did not verify it, but I guess this situation is the same for another Primitive/Object pairs (int/Integer, long/Long ... etc). 
Such conversion is neccessary when parameter is primitive, but in case Object values it is harmfull since null is proper value and has meaning. 
So it would be usefull to avoid this conversion in case Object parameters, especially if in case another onjects it acts as expected (nulls are passed as nulls). 


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira