Thank you Alex for your answer. I am using Tapestry 5.1.0.5. So about beans I think they should be accessible too but and another bean (ProviderManager) declared in the same SecurityModule class actually is used inside XML. I dont understand why the AccessDecisionManager can't ... About spring security, I thought that good practice is to secure the middle tier, and the security used in the view (Tapestry) is more likely hiding useless feature to the user who can't use it and redirect to forbidden page. Thought that T-S-S would do both for me.
You're talking about an article on a Wiki to use S-S without T-S-S, cant you send me the link of this Wiki ? Thank you. Nicolas. > -----Message d'origine----- > From : Alex Kotchnev > To : Tapestry users > Objet : Re: TSS add custom voter & securing non-tapestry methods > > Nicolas, > which T5 version are you using? AFAIK, w/ T5.1 and later your T5 services > should indeed be accessible as Spring beans. I think before 5.1, they > aren't. > Regarding T-S-S : it's set up to handle Tapestry component security (that > is, securing whole components or methods within the components). It does > nothing to handle @Secured annotations on any random classes within your > application. Overall, it seems to me that what you're trying to achieve > should be achievable using plain S-S. If you do need to secure access to T5 > pages, you might be able to achieve that w/o T-S-S (there's an article on > the wiki on using S-S w/o T-S-S). > > Regards, > > Alex Kotchnev --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
