[ https://issues.redhat.com/browse/WFLY-9440?page=com.atlassian.jira.plugin... ] Tomasz Adamski updated WFLY-9440: --------------------------------- Description: EJB has 'enable-jacc' attribute which, if true, result in the code doing a service dep using the org.wildfly.security.jacc-policy capability. But there's no registration of a requirement for that capability, so if it were removed (which requires reload) the inconsistent model would not be detected and a subsequent reboot/restart would fail. This can't be fixed until WFCORE-3354 is, because right now that capability isn't registered either! Fixing this isn't as simple as recording this as a fixed requirement of the relevant ejb/undertow capability, as it's only a requirement if the attribute value is 'true'. was: Both EJB and Undertow have 'enable-jacc' attributes which, if true, result in the code doing a service dep using the org.wildfly.security.jacc-policy capability. But there's no registration of a requirement for that capability, so if it were removed (which requires reload) the inconsistent model would not be detected and a subsequent reboot/restart would fail. This can't be fixed until WFCORE-3354 is, because right now that capability isn't registered either! Fixing this isn't as simple as recording this as a fixed requirement of the relevant ejb/undertow capability, as it's only a requirement if the attribute value is 'true'. -- This message was sent by Atlassian Jira (v7.13.8#713008)