Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[WFLY-9176] Don't clone the entire resource tree to check for the pre…
…sence of another subsystem resource TODO Why not use capabilities for this?
- Loading branch information
1 parent
4d34cb7
commit 13fef10
Showing
2 changed files
with
22 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
13fef10
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bstansberry These two blocks of code only exist to maintain configuration compatibility with AS 7.2. I intend to remove them completely once this compatibility constraint is lifted. The requisite capability references are already in place.
13fef10
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@pferraro This in general is a good topic for the eap-pm list or some other discussion with PM. AS 7.2 became EAP 6.1. We only require mixed-version domains to work for 6.2 or later slaves. We've wanted general API compatibility beyond that but as time passes it's worth considering dropping really old things so we can prune code.
13fef10
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@bstansberry By AS 7.2, I mean the release stream that would continue through EAP 6.4. To be specific, without these blocks of code, the default configuration shipped with EAP 6.4 would fail model validation due to missing required capabilities. So this has less to do with mixed domains, and more to do with validity of legacy configuration defaults. I'll file a JBEAP jira to track this.