You are very welcome. See here for documentation and examples of using tapestry expression language: http://tapestry.apache.org/property-expressions.html
Best, Jacob -----Original Message----- From: David Siedlecki [mailto:david.siedle...@beatsystems.com] Sent: 12. april 2013 13:28 To: Tapestry users Subject: Re: How Tapestry handles null values in template Thank you!!! That's bugged me for ages. Had no idea you could do that. ----- Original Message ----- From: "Jacob Poder" <jacob.po...@thermofisher.com> To: "Tapestry users" <users@tapestry.apache.org> Sent: Friday, 12 April, 2013 12:17:26 PM Subject: RE: How Tapestry handles null values in template Hi, Try ${person?.name} Best, Jacob -----Original Message----- From: David Siedlecki [mailto:david.siedle...@beatsystems.com] Sent: 12. april 2013 13:15 To: users@tapestry.apache.org Subject: How Tapestry handles null values in template Hi. In my template I can do this... ${person.name} if name is null, Tapestry handles that in a nice way and displays an empty string instead of thrown a null pointer exception. if person is null however, it returns an error which means I often have to write custom getter methods in my page class to check for null person objects myself. I'd rather tapestry just displayed an empty string in the rendered page if person or name is null to make my code cleaner. Is is possible to do this? Thanks folks, Dave. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
