jsp:setProperty and bean property naming convention

[Zlatko Marcok]

Hello.
I'm working on my SCWCD using the head first book. I'm trying to send a request directly to a JSP. My test is working, but the naming convention of properties seems inconsistent.

Here is my HTML

    
        <form action="Direct.jsp">
            breed: <input type ="text" name="breed">
            id: <input type="text" name ="ID">
            <input type="submit">
        </form>

This is my Direct.jsp

    
<jsp:useBean
    id="doggy"
    type="UseBeanAction.SuperDog"
    class="UseBeanAction.Dog"
    scope="request">

    <jsp:setProperty name="doggy"  property="breed"/>
    <jsp:setProperty name="doggy"  property="ID"  />

</jsp:useBean>

The doggy breed is: <jsp:getProperty name="doggy" property="breed" />
<br>
The doggy id is: <jsp:getProperty name="doggy" property="ID" />

Everything works as expected with the breed property. The methods are getBreed and setBreed so the bean property is breed with a lowercase 'b'. Correct ?

But ID is different. It seems that because the second character is upper case, the convention is no longer to strip off get/set and replace the first character with its lowercase. The convention is just to strip off get and set.

Am I correct ?

My second question is can this property setting be done with anything other than String property types? If my set methods take integers, is there a way to have the conversion done in the jsp?

Thanks for your consideration.

[Sebastian Janisch]

Your setter method needs to be called setID(String id);

Your properties may also be primitive types, the framework does the type conversion for you in case the input is valid.

[Bear Bibeault]

Things can go easily awry when the bean conventions are violated.

When I have a property for an id (obviously a common need), I always use setId() and getId() so that I can use the normal convention of "id" as the property name.

I don't recommend following the example of "ID".

[Sebastian Janisch]

Bear Bibeault wrote:Things can go easily awry when the bean conventions are violated.

When I have a property for an id (obviously a common need), I always use setId() and getId() so that I can use the normal convention of "id" as the property name.

I don't recommend following the example of "ID".

Yes, the convention for variable names says that (except constants) variables start lowercase and then follow the camel case principle.