And, of course, the other alternative is to provide your own VariableResolver/PropertyResolver that "fixes" this special case, and does what you expect.
You can take a look at the jsf-spring sourceforge project as an example of an alternate resolver that handles special cases while delegating normal cases to the standard resolver. On 10/12/05, Mike Kienenberger <[EMAIL PROTECTED]> wrote: > Well, the thing to do is to discover if it's a bug in the EL > (Expression Language), or if it's expected behavior. You'll have to > look at the JSP specification to determine that since the JSF spec > defers to that document for EL.. > > If it's a bug, resubmit it (preferably with a patch) to commons-el. > I'm pretty sure that's the right place. > > On 10/12/05, Navid Vahdat <[EMAIL PROTECTED]> wrote: > > Seems to be a known bug: http://issues.apache.org/jira/browse/MYFACES-31 > > > > Now the question is how can I solve it. I don't have complete control > > over the attribute names... > > > > Navid > > > > Navid Vahdat wrote: > > > Hi Guys! > > > > > > It seems that I can't have bean properties like "xTest", where the > > > second letter is upper case. A PropertyNotFoundException is thrown from > > > PropertyResolverImpl.getPropertyDescriptor (Line 448 in the nightly > > > build I'm using). Can anyone confirm this? > > > > > > Cheers, > > > Navid > > > > >
