ContextFinder always load the JAXBContext from jaxb-runtime 2.3.3

[jimma]

After upgrading to jaxb-runtime 2.3.3, there is a new created provider file /META-INF/services/javax.xml.bind.JAXBContextFactory
to load and create JAXBContext implementation, and this provider file doesn't exist in previous version like jaxb-runtime-2.3.2 . ContextFinder follows this order to discover the service implementation:

1. Provider of javax.xml.bind.JAXBContextFactory is loaded using the service-provider loading facilities, as defined by Java SE Platform, to attempt to locate and load an implementation of the service. 
2 . Look for resource /META-INF/services/javax.xml.bind.JAXBContext. If such a resource exists, its content is assumed to be the provider factory class.

As a consequence of this order, The JAXBContex from jaxb-runtime 2.3.3 will be always loaded if there is jaxb-runtime 2.3.3 under server's common lib and jaxb-runtime 2.3.2 lib under /WEB-INF/lib. For the servlet container , load class with this order like what Tomcat does won't work anymore :

• Bootstrap classes of your JVM
• ./WEB-INF/classes of your web application
• ./WEB-INF/lib/*.jar of your web application
• System class loader classes
• Common class loader classes (server common lib)

[jimma]

This issue is moved from jakartaee/jaxb-api#157.
with this two comments:

• ContextFinder always load the JAXBContext from jaxb-runtime 2.3.3  jakartaee/jaxb-api#157 (comment)
• ContextFinder always load the JAXBContext from jaxb-runtime 2.3.3  jakartaee/jaxb-api#157 (comment)

[lukasj]

I believe #1514 here together with jakartaee/jaxb-api#177 and jakartaee/jaxb-api#176 on the API side are going to resolve this problem.