tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David White <dw11...@onemail.at>
Subject Re: PATCH: fix for asset service (branch-3-0 2005-03-16)
Date Mon, 21 Mar 2005 10:22:35 GMT
On Mon, 2005-03-21 at 12:12 +0200, Mind Bridge wrote:
> Hi,
> We have been thinking about that approach earlier, but it has a problem:
> when the application is restarted, the pool will no longer contain the
> asset, but its URL will be out there, on cached/bookmarked pages or the
> like. If the asset is not tied to a page, which is possible as well as it
> can be declared in code for example, it gets interesting too.
> In short, it is possible to receive "access denied" errors after a server
> restart even though the asset is completely valid.

No, it isn't. If the server is restarted, the specification will have to
be reloaded and rendered.


To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org

View raw message