[jboss-jira] [JBoss JIRA] (WFLY-11810) Fix 'org.jboss.msc.Service' API to enable proper service installation

[Richard Opalka (Jira)]

    [ https://issues.jboss.org/browse/WFLY-11810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703885#comment-13703885 ] 

Richard Opalka commented on WFLY-11810:
---------------------------------------

This is not MSC API problem [~jstourac].
org.jboss.msc.service.Service.getValue() method is deprecated:
https://github.com/wildfly/wildfly/pull/12012/files#diff-6de66bee9c455ef41784bbcbe049ce8dR58
If you need to use this method you either:
a) didn't migrate your MSC services properly
b) or there are still some internal WildFly APIs that are still using legacy MSC API and thus your code cannot be migrated to new MSC APIs yet

Migration of WildFly code base to use new MSC API is a long process and it will take some time to get there.

> Fix 'org.jboss.msc.Service' API to enable proper service installation
> ---------------------------------------------------------------------
>
>                 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)