we have certain actions we perform in the tapestry lifecycle methods that are application-specific
this is done both when a new page is created and before an existing page is retired to the pool now the problem is that when the same page object is returned, our retirement/creation logic is affected hence we're looking for a way to create a new instance of the page even though the cycle might already have instantiated the page once before Thanks, karthik On 4/16/07, Christian Haselbach <[EMAIL PROTECTED]> wrote:
Quoting Karthik N <[EMAIL PROTECTED]>: > I have a requirement however where I want newPage to be a different > instance than this In that case you should probably rethink the requirement. Why do you want to have a different instance? The concept of the page is that you have an instance to render for the user and then it is returned to the page pool. > Any ideas how this can be achieved? You could turn off the cache, but this is most certainly not what you want. Regards, Christian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Thanks, Karthik --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
