AFAIK its a class loader issue, and thus a container one: check your
tomcat configuration - or whatever container you use, to reload the
context on classpath changes...
Cheers,
Ron
Norbert Sándor wrote:
Hi,
I change an annotation in a component class, then I perform a reset. But
the annotation is not reprocessed, Tapestry still sees the old value. I
use 4.0.
Is this a bug, or does it have a deeper cause (like JVM limits)?
Regards,
Norbi
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
