javax.el.PropertyNotFoundException: using JSTL in JSP [duplicate]

Answer 1

Your getter method doesn't follow the JavaBeans naming convention. It should be named getRssFeedURLs (even if you have an acronym, it should be capitalized like a regular word). In EL, when you specify a property name, it actually ends up calling the getter for that property. To figure out the name of the getter, it capitalizes the first letter in the property name that you have provided (so rssFeedURLs gets converted to RssFeedURLs) and tacks on get to the front of it. So you end up with getRssFeedURLs. However, you have named your method as getRSSFeedURLs. Java can't find the method and so you get a PropertyNotFoundException exception.

If you don't name your getters right, you cannot access them with EL.

Answer 2

If the property name starts with two or more subsequent capitals, then it should be accessed like that in EL as well. So, to access the getter getRSSFeedURLs() you need ${rssfom.RSSFeedURLs}.

That's specified in JavaBeans Spec as well.

8.8 Capitalization of inferred names.

When we use design patterns to infer a property or event name, we need to decide what rules to follow for capitalizing the inferred name. If we extract the name from the middle of a normal mixedCase style Java name then the name will, by default, begin with a capital letter. Java programmers are accustomed to having normal identifiers start with lower case letters. Vigorous reviewer input has convinced us that we should follow this same conventional rule for property and event names.

Thus when we extract a property or event name from the middle of an existing Java name, we normally convert the first character to lower case. However to support the occasional use of all upper-case names, we check if the first two characters of the name are both upper case and if so leave it alone. So for example,

“FooBah” becomes “fooBah”
“Z” becomes “z”
“URL” becomes “URL”

We provide a method Introspector.decapitalize which implements this conversion rule.

The JSP EL (Expression Language, those ${} things) adheres the JavaBeans Spec. This is thus not specifically related to JSTL (those <c:xxx> tags).

Answer 3

My VO has a following code

 public class DocumentPolicyVO {
          @JsonProperty("Id")
            private String Id;
            @JsonProperty("Id")
            public String getId() {
                return Id;
            }
     @JsonProperty("Id")
            public void setId(String Id) {
                this.Id = Id;
            }
    }

When I am trying to access it in a jsp page as below, it is giving following error javax.el.PropertyNotFoundException: Property 'Id' not found on type DocumentPolicyVO

<select name="settingsListExcludingEnvironmentList" class="selectComboboxCheck">
                                                  <c:forEach var="settingsType" items="${settingsListExcludingEnvironmentList}">
                                                      <option value="${settingsType.Id}">${settingsType.Name}</option>
                                                  </c:forEach>
                                        </select>

Please anybody can explain the reason.