2009/3/24 Ville Virtanen <ville.virta...@cerion.fi>: > > Hi, > > double check that the boolean is not primitive _anywhere_, as then assigning > null to it would coerse the value to false witch is the default in Java if > it is unknown.
I checked it 10 times before. Parameter of component and property of page are not primitive Booleans. Similar behaviour I see in oposite direction. When I set value of component parameter to null, page property gets false, not null. > > The other option is that the type coersion system in T5 handles null values > incorrectly? Is it possible, that so base functionality is buggy in stable release (5.0.18) and nobody noticed it before? Neither unit tests? I can't belive. I still think it's my fault and my lack of understanding. Łukasz --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
