Is there a reason why most if not all of the tags will throw JspException if the looked up Resource is null or not found? I understand that you, the programmer, would want to know if you did not bind an object correctly, but when it comes to production, why would you ever want it to thow the exception? I have an app which allows the user to generate the screen rather dynamically, and instead of creating empty objects and binding those, I simply skip all of those steps and go on with the page generation. It then barfs on itself because of the null exception. Why not generate the empty element (if text, value="", etc., or simply ignore the whole iterate/logic tags)?
The code explicitely throws the exception, so it's not like this is an overlooked bug. I assume there was a reason to do this, I just don't quite get it. I would GLADLY remove the throws and change then tag handling of nulls (set text to "", etc.) if the group would like. Please let me know. __________________________________________________ Do You Yahoo!? HotJobs - Search Thousands of New Jobs http://www.hotjobs.com -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
