Results 1 to 2 of 2

Thread: autowire securityInterceptors

  1. #1
    Join Date
    Jun 2005
    Posts
    2

    Default autowire securityInterceptors

    I'm using a huge amount of beans, and to keep it readable, I've split the huge beans-definitionfile in a lot of small files, each based on a certain entity (i.e. User, Group, Role, etc.). Every file has a bean of the SimpleUrlHandlerMapping, which contains all the mappings refered to specific entity. At startup this is resolved by autowiring.
    To keep the size my objectDefinitionSource of the SecurityIntercepter small, I would like a mechanism, which wires all interceptors by type, just like the HandlerMapping. This way every entity can define it's own securityrules, next to it's mapping.
    I've thought of reasons, why you wouldn't want this solution, but I couldn't find one.
    Anyone who has a suggestion?

  2. #2
    Join Date
    Aug 2004
    Location
    Sydney, Australia
    Posts
    2,768

    Default

    Considered using 0.9.0 / CVS' annotations support? This is probably the most elegant way to put the security configuration attributes with your code.
    Ben Alex
    Project Founder, Spring UAA, Spring Roo and Spring Security

Similar Threads

  1. Replies: 1
    Last Post: Aug 17th, 2005, 01:44 PM
  2. Replies: 2
    Last Post: Jul 18th, 2005, 03:43 PM
  3. autowire and parent bean
    By huydo in forum Container
    Replies: 1
    Last Post: Mar 23rd, 2005, 12:19 AM
  4. Implementing AutoWire at request.
    By Lachezar in forum Container
    Replies: 4
    Last Post: Nov 22nd, 2004, 08:53 AM
  5. Replies: 2
    Last Post: Nov 2nd, 2004, 06:22 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •