Kent Tong wrote:
Filip Hanik - Dev Lists <devlists <at> hanik.com> writes:
sounds like you want the cake and eat it too, follow Yoav's suggestion,
and write a macro so that everytime you update a class you touch a
watched resource after the update has been complete
I really don't understand. What's wrong with reloading a changed webapp
whenever it is accessed?
besides having zero purpose in a production environment?
You've already been presented with so many options, take one of them and
use them, you can accomplish exactly what you are looking for, but I
doubt anyone wants to actually add in code that you are suggesting into
the platform.
Filip
---------------------------------------------------------------------
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]
