[
https://issues.jboss.org/browse/WFLY-11810?page=com.atlassian.jira.plugin...
]
Jan Stourac commented on WFLY-11810:
------------------------------------
I want to mention also WFLY-11387 here, although based on the provided fix, that was
probably a different issue with different root-cause to what this issue is aimed at. So
just for a reference...
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=13687...])
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)