Hello, everyone!
On Wed, Jan 15, 2025 at 10:45 AM Ben Weidig wrote:
> Off the top of my head, I'd say you're right that the problem originates
> from binding an implementation. In this case, the service isn't proxied and
> follows a different lifecycle.
>
Hmm, I wouldn't say Tapestry-IoC as a d
Many thanks Ben – I’ll give that a go.
Cheers,
--
Niran Abeygunawardena
Senior Technical Architect
T +44(0)1223 271264
clarivate.com<https://clarivate.com/>
From: Ben Weidig
Date: Wednesday, 15 January 2025 at 13:45
To: Tapestry users
Subject: Re: Override a class in CSRF protection
Hello,
Off the top of my head, I'd say you're right that the problem originates
from binding an implementation. In this case, the service isn't proxied and
follows a different lifecycle.
See:
https://github.com/apache/tapestry-5/blob/82199021fa646a7ea4f7ccd7a7ea08cccb014b46/tapestry-ioc/src/main/
