[ https://issues.jboss.org/browse/WFLY-6634?page=com.atlassian.jira.plugin.... ] Richard Janík commented on WFLY-6634: ------------------------------------- Agreed with [~pferraro], input from [~bilge] would be helpful on that. I understand injecting RemoteCacheManagers is not supported, that is fine and I do not intend to test it. But the configuration for {{remote-cache-manager}} is still public and supported I assume. Since the PRs add configuration, there needs to be an RFE for that. Right now, EAP7-942 covers only the security configuration for the {{remote-cache-manager}}. As [~mjurc] says: If we want to expose other configuration elements for {{remote-cache-manager}}, the configuration needs to be tested. If we do not want to support such configuration, those configuration elements must not be present in model and other, hidden mechanisms must be used. We’re not asking for 1:1 coupling between WFLY and EAP7 issues, just that anything that is configurable is tracked in EAP7. -- This message was sent by Atlassian JIRA (v7.5.0#75005)