Uploaded image for project: 'Spring Security'
  1. Spring Security
  2. SEC-1835

ID types in schema not conducive to using Spring 3.1 profiles

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.1.0.RC3
    • Fix Version/s: 3.1.0
    • Component/s: Namespace
    • Labels:
      None

      Description

      When using Spring 3.1 profiles, I may want to use <user-service> in a "dev" profile and use <jdbc-user-service> or <ldap-user-service> in a "production" profile. Unfortunately, the ID type on all of the "id" attributes (as well as the ID type of <authentication-manager>'s "alias" attribute) makes it impossible to configure these in different profiles within the same XML configuration file. Changing these attributes to xsd:string (as has been done in the spring-beans XSD) will loosen the restriction and make it possible to configure beans with the same ID under different profiles in the same XML config.

        Activity

        Hide
        luke Luke Taylor added a comment -

        I've switched the id types to use xsd:token.

        Show
        luke Luke Taylor added a comment - I've switched the id types to use xsd:token.

          People

          • Assignee:
            luke Luke Taylor
            Reporter:
            habuma Craig Walls
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: