Brian Stansberry created WFCORE-52: -------------------------------------- Summary: Create alternative to /core-service=module-loading:list-resource-loader-paths for identifying what module a jar came from Key: WFCORE-52 URL: https://issues.jboss.org/browse/WFCORE-52 Project: WildFly Core Issue Type: Feature Request Security Level: Public (Everyone can see) Components: Domain Management Reporter: Brian Stansberry The /core-service=module-loading:list-resource-loader-paths used to be a mechanism for identifying from what module a resource was loaded, because the path would point the the module. GSS made use of that for analyzing where things come from in a situation with multiple module roots (e.g. a layered product.) But with the addition in module.xml of the "artifact" element alternative to the "resource" element, the returned path may no longer point to the module; it may point to a maven repo path. So we need some other API method to meet the use case of identifying from what module root a module was loaded. -- This message was sent by Atlassian JIRA (v6.2.6#6264)