On Tuesday 19 Mar 2002 14H:11 pm, you wrote: > On Mon, 18 Mar 2002, John Baker wrote: > > That's a real minus point for JSTL. > > In defense of the way JSTL currently works, this isn't really its job. > The design standard for components is JavaBeans, which outlines what's a > property and what's not.
Yes, I see there is the need for simple coding practises, but it makes design of good beans/servlets harder. For example, when I'm designing Java beans, I declare all my attributes as static, so I have: public static final String COST = "cost"; public double getCost(); public void setCost(double d); So if I ever have to change the method name, my JSP pages won't break ;-) When I was reading the spec, I got the impression this was possible: (section 6.1.5) <c-rt:out value="<%= SomeClass.COST %>"/> So I'm assuming that the c-rt tld will evaluate SomeClass.COST as "the variable COST in the class SomeClass". But that doesn't seem to work either :-) Cheers John -- John Baker, BSc CS. Java Developer, TEAM/Slb. http://www.teamenergy.com Views expressed in this mail are my own. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
