[
https://issues.jboss.org/browse/AS7-5522?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry updated AS7-5522:
----------------------------------
Fix Version/s: 7.2.0.CR1
(was: 7.2.0.Alpha1)
I don't want to touch this unless we have a clear use case for how more than one
content item would be supported. Unless there is more than one, we are better off
flattening out the list element attributes and putting them in the root deployment
resource.
It's a list because of a desire for clear ordering. Multiple content items would be
overlaid on top of each other.
Deployment overlays cover much the same use case, so I'm not sure we'll ever want
to support multiple content items in this resource.
The ordering semantics could be done with child resources, but it would require a special
resource type and ops to move the resource around.
Moving to 7.2.0.CR1 since for sure we aren't going to change this for Alpha1.
Convert deployment's content to a child resource
------------------------------------------------
Key: AS7-5522
URL:
https://issues.jboss.org/browse/AS7-5522
Project: Application Server 7
Issue Type: Feature Request
Components: Domain Management
Reporter: Kabir Khan
Assignee: Brian Stansberry
Fix For: 7.2.0.CR1
At the moment this is a complex attribute.
Not saying this MUST happen, just opening this to see what Brian & co think. I never
really understood why it is a list either.
--
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