tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim Funk <>
Subject Re: 2 Questions ..
Date Fri, 10 Oct 2003 15:36:50 GMT
Its probably the java compiler. If your constant is declared final, the 
compiler may be performing an optimization and taking the value insteadof a 
run-time reference. You can get around this by not using a constant and using 
a get method.


Mufaddal Khumri wrote:

> Hi,
> Am running my webapp under tomcat 4.1.18. Everything was fine till  
> yesterday. I am facing this issue today. I wrote a new taglib -  
> nextPrevLink for a jsp page called PotatoList.jsp.
> <cw:nextPrevLink listSize='<%= getTotalNumberOfPotatoes()%>'
>                          offset='<%=offset%>'
> displaySize='<%=Constants.POTATO_LIST_DISPLAY_SIZE%>'
>                          link='someLink'/>
> Now when i change the value of the Constants.POTATO_LIST_DISPLAY_SIZE  
> in the and "reload" my webapp thru the tomcat manager  
> and go to PotatoList.jsp the taglib takes the old value of displaySize  
> (I have a system.out.println("") .. inside the class that implements  
> the taglib).
> Now if i change the PotatoList.jsp and "save it again" ... tomcat  
> recompiles PotatoList.jsp when it comes across it. This time the taglib  
> nextPrevLink takes the correct new value of Constants.  

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message