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

[WFCORE-57] : Deprecated resource is present in r-r-d of /subsystem=security/security-domain=* #118

Merged
merged 1 commit into from Sep 24, 2014

Conversation

ehsavoie
Copy link
Contributor

Aliases were displayed without their description even if include-aliases is not set to true.
Now the operations 'read-resource-description' and 'read-children-types' won't display aliases per default.

Jira: https://issues.jboss.org/browse/WFCORE-57

@wildfly-ci
Copy link

Build 232 is now running using a merge of 4fb1efb

@wildfly-ci
Copy link

Build 232 outcome was SUCCESS using a merge of 4fb1efb
Summary: Tests passed: 2548, ignored: 56 Build time: 0:15:34

if (registredNames != null && !registredNames.isEmpty()) {
for (String value : registredNames) {
ImmutableManagementResourceRegistration childRegistration = registry.getSubModel(PathAddress.pathAddress(PathElement.pathElement(key, value)));
isAlias = isAlias && childRegistration != null && childRegistration.isAlias();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Assume this is a "singleton" fka "squatter" situation (see [1])...

Then wildCardChildRegistration will be null, so from L220 isAlias will be false, so the result of L225 will always be false.

This means a singleton/squatter could never be processed as an alias. But such a registration could be an alias.

Are lines 219-200 needed? Can declaring isAlias = true to start and then setting to false and breaking the loop if childRegistration.isAlias() work?

[1] http://lists.jboss.org/pipermail/wildfly-dev/2014-August/002701.html

@wildfly-ci
Copy link

Linux Build 430 is now running using a merge of dd473cf

@wildfly-ci
Copy link

Windows Build 181 is now running using a merge of dd473cf

@wildfly-ci
Copy link

Linux Build 430 outcome was SUCCESS using a merge of dd473cf
Summary: Tests passed: 2595, ignored: 56 Build time: 0:16:13

@wildfly-ci
Copy link

Windows Build 181 outcome was FAILURE using a merge of dd473cf
Summary: Execution timeout (new); tests passed: 2414, ignored: 44; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:30:06

Build problems:

Execution timeout
Process exited with code 1

@wildfly-ci
Copy link

Windows Build 182 is now running using a merge of dd473cf

@wildfly-ci
Copy link

Linux Build 431 is now running using a merge of dd473cf

@wildfly-ci
Copy link

Windows Build 182 outcome was SUCCESS using a merge of dd473cf
Summary: Tests passed: 2595, ignored: 56 Build time: 0:13:18

@wildfly-ci
Copy link

Linux Build 431 outcome was SUCCESS using a merge of dd473cf
Summary: Tests passed: 2595, ignored: 56 Build time: 0:16:10

@@ -817,7 +858,7 @@ public void execute(OperationContext context, ModelNode operation) throws Operat

public static AccessControl forName(String localName) {
final AccessControl value = localName != null ? MAP.get(localName.toLowerCase()) : null;
return value == null ? AccessControl.valueOf(localName.toUpperCase(Locale.ENGLISH)) : value;
return value == null ? AccessControl.valueOf(localName.toUpperCase()) : value;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason we're removing the locale? It seems it should be left there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nope

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No reason, or no we shouldn't leave it there?

Because we should leave it there.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No reason, I'm going to add it back

…ecurity/security-domain=*

Aliases were displayed without their description even if include-aliases is not set to true.
Now the operations 'read-resource-description' and 'read-children-types' won't display aliases per default.
Trying to take "squatter" resource into account for alias.
@wildfly-ci
Copy link

Windows Build 188 is now running using a merge of 825802e

@wildfly-ci
Copy link

Linux Build 438 is now running using a merge of 825802e

@wildfly-ci
Copy link

Windows Build 188 outcome was SUCCESS using a merge of 825802e
Summary: Tests passed: 2595, ignored: 56 Build time: 0:13:58

@wildfly-ci
Copy link

Linux Build 438 outcome was SUCCESS using a merge of 825802e
Summary: Tests passed: 2595, ignored: 56 Build time: 0:16:01

bstansberry added a commit that referenced this pull request Sep 24, 2014
[WFCORE-57] : Deprecated resource is present in r-r-d of /subsystem=security/security-domain=*
@bstansberry bstansberry merged commit d10e3eb into wildfly:master Sep 24, 2014
@ehsavoie ehsavoie deleted the WFCORE-57 branch December 5, 2014 09:14
iweiss pushed a commit to iweiss/wildfly-core that referenced this pull request Jun 6, 2016
JBEAP-1703 Standalone powershell script does't support SECMGR=true
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
5 participants