Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
spring-projects-issues opened this issue Oct 6, 2011 · 1 comment

Comments

@spring-projects-issues
Copy link

@spring-projects-issues spring-projects-issues commented Oct 6, 2011

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.

@spring-projects-issues
Copy link
Author

@spring-projects-issues spring-projects-issues commented Oct 21, 2011

Luke Taylor said:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants