[Delayed response, ignore if no longer interesting]
I've worked with the introspector, and, while I'm also too busy/lazy
to test I'm reasonably sure that it works this way because the first
character gets lowercased before the property name is passed onto the
java.beans Introspector (and before it's passed to Velocity's
Uberspect)
IMO, it's a sensible design choice, since, by the java bean spec,
properties are always named with a leading lowercase character
(xxxXxx) but the accessors will always have the first character of
the property uppercased (getXxxXxx); being forgiving here avoids a
potential source of confusion for non-coders.
eric
So that means it already is, in the case of $foo.xxx and $foo.Xxx?
(That was not a rhetorical question. I am still learning
velocity and really curious to know.)
Honestly, I'm not entirely sure of the outcome because I've never put
objects into the template that have potential conflic based on case
sensitivity. The introspector tries to access data on the object in a
set order, and so I believe both of these would try traditional
beanspec
case first and therefore find foo.getXxx() and then stop looking
deeper.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
