In case someone can help you:
We have managed to avoid the message by following the same instructions indicated in the response link for the implementation of DocumentBuilderFactory. Where reference is made to the official JAXP documentation [Java EE]:
When an application wants to create a new JAXP DocumentBuilderFactory instance, it calls the staic method DocumentBuilderFactory.newInstance (). This causes a search for the name of a concrete subclass of DocumentBuilderFactory using the following order:
The value of a system property like javax.xml.parsers.DocumentBuilderFactory if it exists and is accessible.
The contents of the file $ JAVA_HOME / jre / lib / jaxp.properties if it exists.
The Jar Service Provider discovery mechanism specified in the Jar File Specification. A jar file can have a resource (i.e. an embedded file) such as META-INF / services / javax.xml.parsers.DocumentBuilderFactory containing the name of the concrete class to instantiate.
The fallback platform default implementation.
Following the steps, we have created the file META-INF / services / javax.xml.soap.SAAJMetaFactory indicating the default implementation to use:
com.sun.xml.messaging.saaj.soap.SAAJMetaFactoryImpl
And with this the message has stopped appearing.