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

Add support for indicating than an XML element is deprecated #24237

Closed
odrotbohm opened this issue Dec 20, 2019 · 1 comment
Closed

Add support for indicating than an XML element is deprecated #24237

odrotbohm opened this issue Dec 20, 2019 · 1 comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement

Comments

@odrotbohm
Copy link
Member

To safely deprecate XML elements from namespaces it would be nice to be able to express that deprecation in the XSD for the namespace. Spring already defines a tool namespace that contains information to let IDEs evaluate information to apply additional verifications, show warnings etc.

A new <tool:deprecation …> element could take a message attribute that'd allow XSD authors to mark an element as deprecated and provide additional information to give users a hint to what to use instead and also when they have to expect the eventual removal of that element.

@martinlippert indicated he'd already be looking into what it'd take to let the current generation of STS use such element. I guess it's worth pinging the IntelliJ folks as well.

@odrotbohm odrotbohm added in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement labels Dec 20, 2019
@rstoyanchev rstoyanchev added the status: waiting-for-triage An issue we've not yet triaged or decided on label Jan 10, 2020
@snicoll snicoll changed the title Add new <deprecation … /> element in the tool namespace Add support for indicating than an XML element is deprecated Sep 20, 2023
@jhoeller jhoeller removed the status: waiting-for-triage An issue we've not yet triaged or decided on label Dec 21, 2023
@jhoeller jhoeller added this to the General Backlog milestone Dec 21, 2023
@jhoeller
Copy link
Contributor

Since we intend to phase out XML bean definitions and in particular XML configuration namespaces, it does not seem necessary to introduce a deprecation mechanism for individual elements anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: core Issues in core modules (aop, beans, core, context, expression) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

3 participants