Details
Description
It is due to in OSGi container, the spring PathMatchingResourcePatternResolver doesn't know the bundle:// URL so can't scan the package and get the resource.
If it's in OSGi container and spring-dm (1.2 style) is used, we can set the TCCL as bundle BundleDelegatingClassLoader and use OsgiBundleResourcePatternResolver to scan the package inside a certain bundle.
Though in OSGi the blueprint configuration is suggested to use and we actually have another issue[1] to add blueprint support for jaxrs auto-discovery, add spring-dm 1.2 support should be good also as people may still use it.
[1]https://issues.apache.org/jira/browse/CXF-5848