I'm glad your just as confused as I am, since I honestly don't know either :)
I was hoping you'd have the magic answer, but looks like I'll have to dig around this weekend to figure what the exact cause is. thanks for responding to my obtuse questions, since I'm confused as to why this behavior happens at all. I'll post what ever I find, hopefully detailed information about how to reproduce or track it down. peter Shawn Bayern wrote: > > On Fri, 18 Oct 2002, peter lin wrote: > > > it's only when the syntax is incorrect that it doesn't throw an > > exception like "symbol cannot be resolved", "clascastexception" or > > some other exception. Right or wrong, I expect the EL to realize > > "duh, that's the wrong syntax silly pete. I'm throwing an exception." > > Which EL expression causes this? If the syntax of an expression isn't > parseable, the EL should throw an exception. If the property is simply > unknown, the behavior can depend on whether we're dealing with a Map or > JavaBean; it's all defined by the spec. > > Since our JSTL implementation doesn't directly produce logs, I'm just > trying to figure out *exactly* what you're doing that does produce logs, > and then trace it back to the code that ultimately causes them to be > created. Ideally, you'd have a minimal pair of two *identical* fragments, > one of which uses the EL and produces the erroneous logs, and one of which > doesn't. > > Sorry if I'm being obtuse; I'm just not understanding the problem reports, > or I'm missing some information. > > Shawn > > -- > To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> > For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org> -- To unsubscribe, e-mail: <mailto:taglibs-user-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:taglibs-user-help@;jakarta.apache.org>
