Services are used to bring this data into the ModifiableResourceAdapter, the entire process of populating the data becomes multi-threaded, and therefore more complex and fragile. OTOH, if, when RaOperationUtil.buildResourceAdaptersObject is invoked, the Resource tree is in a state where all the relevant config information is present, the thread invoking RaOperationUtil can simply read that data and populate the object. Single threaded.

Consider the full lifecycle of RA resource and subresource:

RA can be added boot time reading xml and immediately activated
RA can be added runtime by :add operations and then manually activated calling :activate operation
I think the point is to run this RaOperationUtil.buildResourceAdaptersObject with all information presents. The bug should only at boot time though because in latter case is reponsible of human user/batch to call :activate only when all resources have been created.

More context information can be found at PR: https://github.com/wildfly/wildfly/pull/8592