makes a reference variable called myCar to your bean class CarBean
your editor thinks you are not using it or reading it maybe because you are using the JSP getProperty and setProperty which the editor may not understand or interpret as reading or using that reference variable.
If you where to make a reference to the bean class method or member variable in a jsp expression like this <%=myCar.getMake()%> or <%=myCar.make%> the warning from the editor might go away(i'm not sure ). Also, I'm not saying you should do it that way either, because it is best to follow the recommended way of doing things according to the specifications and if that is <JSP:set and <jsp:get then use those, but as Bear said, try to rely less on the editor. I also use eclipse and it becomes a very valuable tool when writing classes as opposed to JSP in my opinion, but once you know JSP good, then you need not worry about those warnings and you might also end up with no java code in your jsp at all where instead you use tags. [ August 13, 2006: Message edited by: Stu Higgs ]
Thanks so much for the time you took in helping to understand what it going on. I did get a NEW JSP book yesterday in hopes that I will be able to better understand WHY some code appears with warnings.
I am truly not trying to rely on the IDE but there was no explanation in the book or the IDE and therefore the reason for my post.
Stu, thanks so much for your explanation. It really helped.
If you are planning on using Eclipse, you might try using the Eclipse Web Tool Platform. It tends to be pretty good at picking out syntax errors in jsps. Just don't try to use refactoring, it's bad at refactoring jsps.