[
https://issues.jboss.org/browse/AS7-5112?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry commented on AS7-5112:
---------------------------------------
Does it fail if "roles.deprecated" does not exist? It shouldn't.
For AS 8 we should change the ResourceDescriptionResolver interface and the standard impl
to properly handle this. With the standard impl doing the "roles.deprecated"
behavior we'd already introduced.
Add deprecation information to management API metadata
------------------------------------------------------
Key: AS7-5112
URL:
https://issues.jboss.org/browse/AS7-5112
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Brian Stansberry
Assignee: Tomaz Cerar
Fix For: 7.3.0.Alpha1
Add metadata describing that we have deprecated:
1) Resources
2) Attributes
3) Operations
4) Operation parameters
We'll need to sort out exactly what info to provide. We can declare in what
management API version an item was deprecated, and provide some localized text explaining.
More problematic would be info on what "version" the item will be removed in
(outside of vague wording in the description text). Probably including such info would be
a mistake; prone to error.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira