That is correct. It is a problem that i caused by property resolver. It
internally uses the Introspector to get all the properties and their
accessor methods and any other methods.

In a special case like - "sOmeBean" this will cause a problem because of
decaptilization.

On 12/20/06, Mike Kienenberger <[EMAIL PROTECTED]> wrote:

Yes, the naming gets a little odd when you start using consequetive
uppercase letters.

For instance, bean.UIDisplayLabel for getUIDisplayLabel()

You might try userSettingsBean.QType.


On 12/20/06, Mikael Andersson <[EMAIL PROTECTED]> wrote:
> Hi,
>  I think it is the naming of the property "qType" which causes this.
>  Just tried myself to make sure, because I thought it should work to
have
> one lowercase character before a uppercase one, but it didn't work for
me
> either.
>  So renaming the property might solve you problem.
>
>  - Mike
>
> On 20/12/06, Greg Reddin <[EMAIL PROTECTED]> wrote:
> > BTW, here's the relevant portions of my managed beans since I'm sure
> > someone will ask me to check my spelling, etc :-)
> >
> > public class ReportingBean extends ActionController {
> > ....
> >    private String qType;
> > ...
> >    public String getQType() {
> >        return qType;
> >    }
> >
> >    public void setQType(String qType) {
> >        this.qType = qType;
> >    }
> >
> > }
> >
> > public class UserSettingsBean extends ActionController  {
> > ....
> >    private String qType;
> > ...
> >    public String getQType() {
> >        return qType;
> >    }
> >
> >    public void setQType(String qType) {
> >        this.qType = qType;
> >    }
> >
> > }
> >
> > Thanks,
> > Greg
> >
>
>




--
When I tell the truth, it is not for the sake of convincing those who do not
know it, but for the sake of defending those that do

Reply via email to