> The issue is how to implement a null check logic in tml. Lets say we have an object User and an Address, now if > address is not null I want to display something different. > If I use: > <t:if test="user.address"> or <t:unless test="!user.address">
So Tapestry already does what you want (checks for null) and it works. This isn't a bug. What you really want is a direct Object -> Boolean coercion to avoid the use of toString() in checks. This is a performance improvement. Is there any reason for Tapestry-IoC or Tapestry-core themselves not providing a direct Object -> Boolean coercion? Denis, you can still provide it directly now while Tapestry-IoC doesn't, so I against applying your patch while I agree with the performance enhancement. Cheers! Thiago -- View this message in context: http://tapestry.1045711.n5.nabble.com/Null-check-property-expression-syntax-tp4726386p4731096.html Sent from the Tapestry - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org For additional commands, e-mail: dev-h...@tapestry.apache.org
