The JavaBean Specification defines explicit naming rules for properties
and their getter/setter methods as well as conventions for their method
signatures. If you deviate from those rules and conventions in any way,
your bean is no longer compliant with the spec.
What you had was 'a proper bean' but since the getter method was
mis-spelt, that property wasn't recognized. It's well worth reading the
few short sections of the spec that deal with these naming conventions
to avoid getting into trouble in the future.
L.
[EMAIL PROTECTED] wrote:
Hi,
You were right. It was the capitalization that was wrong.
Actually I didn't understood the comment about javabean as in my eyes it was a
proper bean.
Your apology about null is taken!
I've seen problems in other places in our code that I need to investigate if it
is the same problem!
Thanks for all help!
/Gunnar
-----Ursprungligt meddelande-----
Från: Dale Newfield [mailto:[EMAIL PROTECTED]
Skickat: den 7 oktober 2008 17:39
Till: Struts Users Mailing List
Ämne: Re: SV: SV: Ognl versions
[EMAIL PROTECTED] wrote:
We have a measureList that looks the same and it works!
It's not quite the same, since it's capitalization is correct.
public SortedMap<Integer, String> getMeasureList() {
Chris Pratt wrote:
Just as an experiment, you might try renaming the method as a true
JavaBean method. Maybe OGNL got more strict on it's
interpretation
of the spec.
The renaming he's mentioning is from getjobTypeList to
getJobTypeList :
public SortedMap<Integer, String> getjobTypeList() {
And my apologies for misunderstanding your comment about it
being null.
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
