[jboss-jira] [JBoss JIRA] (WFCORE-1852) Logging configuration service for dynamic deployment resources uses wrong service name for deployments

[James Perkins (JIRA)]

James Perkins created WFCORE-1852:
-------------------------------------

             Summary: Logging configuration service for dynamic deployment resources uses wrong service name for deployments
                 Key: WFCORE-1852
                 URL: https://issues.jboss.org/browse/WFCORE-1852
             Project: WildFly Core
          Issue Type: Bug
            Reporter: James Perkins


Ideally if the use of a service can be removed that would be best. What's needed is a way to associate a deployments resource with a {{LogContextConfiguration}}. One option is to use a custom resource that the OSH can get the {{LogContextConfiguration}} from. This is already done for the child resources. See the {{LoggingDeploymentResources}}. The OSH can cast the resource and just get the configuration.

{quote}
[12:08 PM] Brian Stansberry: @jperkins this doesn't look right: https://github.com/wildfly/wildfly-core/blob/master/logging/src/main/java/org/jboss/as/logging/deplo...
[12:09 PM] Brian Stansberry: AFAICT it is using the management name of a deployment to create an MSC ServiceName
[12:10 PM] James R Perkins: @BrianStansberry Hmm. ...yeah. Let me look at why I was doing that.
[12:13 PM] James R Perkins: @BrianStansberry Yes that's what it's doing which thinking about it does seem wrong. Essentially it's trying to figure out which service to use for a dynamic resource on the /deployment=some.war/subsystem=logging/configuration=whatever
[12:14 PM] Brian Stansberry: you need to use the runtime-name attribute of the deployment
[12:14 PM] James R Perkins: Really it's kind of a bad use case for a service.
[12:14 PM] Brian Stansberry: I guess subdeployment has one too, although it's redundant
{quote}



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)