views:

11

answers:

1

I made a custom jsp tag that search a historical value on a database an render it on the page. The attributes that the tag requires are the variable name and the date.

The problem is that the 'date' property changes according clock move on ('date' points always to the last hour), but the JSP Tag processor's (jasper2) pooling system don't update the 'date' property anymore (calling to the setDate), and the page stays freezed on a point in time.

I don't want to disable the pooling system because it gives performance to the web, but i need to tell it somehow that 'date' property must be setted always.

There is a trick o a procedure to force this?

Thanks a lot.

A: 

I am not sure what pooling you are talking about.

Part of the JSP specification that all containers implement is the distinction between attributes evaluated at runtime and those evaluated when the page is compiled.

In the TLD, you must declare the date attribute's <rtexprvalue/> to be true.

erickson
Thanks for the answer. I found the problem: Me. I didn't respect the directive that says that i don't have to change the 'date' property internally. Thanks and sorry for stealing your time.
ejmarino