Thank you Jonathan. Capital letters don't change anything, unfortunately.
Just like you, I came to the conclusion that the few lines I added in XML to enable the security on methods are actually initiating another security context and it implicitly creates what it needs to work. I'll try to customize T-S-S. For now I will work around the small constraints of T-S-S. Thank you again for the time you took investigating this. Nicolas -----Message d'origine----- From : Jonathan Barker [mailto:jonathan.theit...@gmail.com] To : Tapestry users Objet : Re: TSS add custom voter & securing non-tapestry methods There's nothing jumping out at me, so here are a couple of things to try: Change the capitalization on access-decision-manager-ref="accessDecisionManager" to "AccessDecisionManager" and see if it finds your bean. It looks like in the absence of a specific reference, it's building a default configuration of the AccessDecisionManager, giving you duplication. If that doesn't work, try building a custom copy of TSS with the builder for AccessDecisionManager commented out, and build one within the Spring xml file. Good luck. JB Jonathan Barker ITStrategic --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
