SEC-1835: ID types in schema not conducive to using Spring 3.1 profiles #2065

spring-issuemaster opened this Issue Oct 6, 2011 · 1 comment


None yet
1 participant

Craig Walls (Migrated from SEC-1835) said:

When using Spring 3.1 profiles, I may want to use in a "dev" profile and use or in a "production" profile. Unfortunately, the ID type on all of the "id" attributes (as well as the ID type of '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.

Luke Taylor said:

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

spring-issuemaster added this to the 3.1.0 milestone Feb 5, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment