As discussed in MSC-240, different impls of the MSC ServiceBuilder interface will support different subsets of the ServiceBuilder API, throwing UnsupportedOperationException if methods not in that subset are invoked. This makes code that accepts an SB from unknown origins vulnerable to failure if the wrong type of SB is passed in.

JBEAP-15383 is an example of such a failure.

I've done an analysis WildFly and WildFly Core use of ServiceBuilder looking for problematic cases. I will attach the analysis. This JIRA is to fix the items in WF Core that are annotated with the CRITICAL notation.

A possible fix for this is simply incorporating an MSC release that has MSC-240 adequately resolved. (Note that adequate doesn't mean completely fixed; simply preventing problems in the methods annotated as CRITICAL is sufficient.) Barring that a fix would be to avoid or deal with the UOE.