You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resource resource = new ApplicationResourceLoader().getResource(location);
Creating a new ApplicationResourceLoader instance means that for example S3ProtocolResolver from Spring Cloud AWS that works by registering itself using ResourceLoaderAware is ignored and only those declared in spring.factories get picked.
I know there are a few ways to work around this, but it's not that obvious that not all ProtocolResolvers work when declaring a bundle.
The text was updated successfully, but these errors were encountered:
philwebb
changed the title
Support for additional ProtocolResolvers in JksSslStoreBundle
Support ResourceLoader delegation from ApplicationResourceLoader when used with SSL bundles
Oct 22, 2024
I'm currently looking at #42468 and would like a way to have auto-configured SSL Bundles work with the classloader from the application context ResourceLoader. It seems like supporting delegation would be possible once that is fixed.
philwebb
changed the title
Support ResourceLoader delegation from ApplicationResourceLoader when used with SSL bundles
Support ResourceLoader delegation from ApplicationResourceLoader
Oct 23, 2024
Is there a reason that
JksSslStoreBundle
creates a new instance ofApplicationResourceLoader
instead of using an existingDefaultResourceLoader
?https://github.com/spring-projects/spring-boot/blob/main/spring-boot-project/spring-boot/src/main/java/org/springframework/boot/ssl/jks/JksSslStoreBundle.java
Resource resource = new ApplicationResourceLoader().getResource(location);
Creating a new
ApplicationResourceLoader
instance means that for example S3ProtocolResolver from Spring Cloud AWS that works by registering itself usingResourceLoaderAware
is ignored and only those declared in spring.factories get picked.I know there are a few ways to work around this, but it's not that obvious that not all
ProtocolResolvers
work when declaring a bundle.The text was updated successfully, but these errors were encountered: