Hi specialist33 & Nathan,
> > > problem is or else your getLogin() method is returning null. can you
> > assure
> >
> > ! This possibility entirely passed me by (its probably in the docs and I
> > just didn't notice it, but it's very counter-intuitive),
>
> :)
You guys sure got me on this one. At least I learned a lot about
Velocity's internal behaviour. ;)
> but there can be something wrong with displaying unrendered references in a
> template language. thus the warning message.
OTOH, every schmoo that looks like a reference causes a warning
message. Too bad Velocity can't decide whether it was meant to be or
not. (And I don't want to go around telling all the template
designers, use "${dollar}" instead of "$". Although it would make
life for the programmers a lot easier. ;))
> > I'm guessing an even better approach would be two separate messages, one
> > for the "couldn't find a method" and another for "found a method but it
> > returned null", and in both cases it ought to say what the method name
> > it found (or tried to find) was. That would shortcut the debugging
> > process considerably, and probably reduce the number of people in my
> > situation who even needed to come to the list to ask for help :).
>
> yeah, that sounds like a worthy enhancement request. i'd recommend filing a
> bug report on it so it doesn't get forgotten. and, of course, if you can come
> up with a patch to go with it, that would be cool too. i can't say whether
> it'll ever be applied, but i think this is a good idea.
I'll vote on that one. :)
Best regards,
-- Shinobu Kawai
--
Shinobu Kawai <[EMAIL PROTECTED]>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
