I definitely agree with you on this point. While I like how JSTL doesn't
dump error messages in the page, I've spent many bleary-eyed hours trying to
troubleshoot code only to find I was missing something simple like the
example below.
Tracing through code is a bummer and being able to have a little more
feedback is invaluable. Can someone shed some light on why an accessor
function would be a bad thing?
- Nic Werner
Link11
----- Original Message -----
From: "Eric W Hauser" <[EMAIL PROTECTED]>
To: "Tag Libraries Users List" <[EMAIL PROTECTED]>
Sent: Wednesday, July 30, 2003 10:46 AM
Subject: Why no exception with missing accessor?
> While discussing JSTL with some others developers today, a question came
> up about the lack of helpful errors when using JSTL incorrectly. If I use
> the following line of code:
>
> <c:out value="${sessionScope.mybean.value}"/>
>
> and there is no accessor method of value, then JSTL just returns nothing.
> Others said they though it would make more sense if a JspException was
> thrown because you were attemping to access an accessor that did not
> exist. We have a number of custom tag libraries in which I would like to
> add the ability to exception EL expressions, but I'm getting some
> resistance because of this issue. Any thoughts?
>
> -------------------
> Eric Hauser
> [EMAIL PROTECTED]
> (317) 679-4766
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
