[jboss-jira] [JBoss JIRA] (WFLY-11810) Support new MSC Service API for deployment dependency

[Jeff Mesnil (Jira)]

     [ https://issues.jboss.org/browse/WFLY-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jeff Mesnil updated WFLY-11810:
-------------------------------
    Summary: Support new MSC Service API for deployment dependency  (was: Fix 'org.jboss.msc.Service' API to enable proper service installation)


> Support new MSC Service API for deployment dependency
> -----------------------------------------------------
>
>                 Key: WFLY-11810
>                 URL: https://issues.jboss.org/browse/WFLY-11810
>             Project: WildFly
>          Issue Type: Bug
>          Components: MSC
>    Affects Versions: 16.0.0.Final
>            Reporter: Jan Stourac
>            Assignee: Jeff Mesnil
>            Priority: Major
>
> I have no necessary insight regarding to the code but based on the discussion in WFLY-11603 ([comment|https://issues.jboss.org/browse/WFLY-11603?focusedCommentId=13687703&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13687703]) it is not possible to use 'org.jboss.msc.Service' API to properly install service and deprecated 'org.jboss.msc.service.Service' API has to be used instead.
> It is necessary to fix the behavior of the new API so when we switch to it, we don't introduce the issue described and fixed in WFLY-11603 again. As it was an intermittent NPE, there is a risk that during the simple switch from deprecated API the introduced issue is not caught right-away but after some time...



--
This message was sent by Atlassian Jira
(v7.12.1#712002)