-
Notifications
You must be signed in to change notification settings - Fork 38k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add support to enhance default resource loader [SPR-12857] #17455
Comments
Juergen Hoeller commented I've added an SPI called
allowing for resolving a custom protocol if known, or Any number of such resolvers can be registered with a |
Petar Tahchiev commented Hello, I tried to register my own
and then I try to load media |
Brian Clozel commented Hello Petar Tahchiev The current resource handling infrastructure relies on chains of I believe you can register and order your own resolvers and transformers to achieve this goal. Currently, the last In your case, you could create your own If you can think of something we can improve with the current Thanks! |
roll tide commented This looks like fantastic addition. I am in need to extend the existing I am using Spring Boot v1.3.5 and Spring Core v4.3.3 so I was hoping to use this feature but I may be configuring it incorrectly. Is there specific example for reference? I create bean of type |
Agim Emruli opened SPR-12857 and commented
There are a few implementations of the resource loader already available that support custom protocols like S3 (https://github.com/spring-cloud/spring-cloud-aws/blob/master/spring-cloud-aws-core/src/main/java/org/springframework/cloud/aws/core/io/s3/PathMatchingSimpleStorageResourcePatternResolver.java) and HDFS (https://github.com/spring-projects/spring-hadoop/blob/master/spring-hadoop-core/src/main/java/org/springframework/data/hadoop/fs/HdfsResourceLoader.java)
that can not register easily within the application context. It would be great if the Spring Framework would allow to register some custom ResourceLoader so that the default one can be overriden and then used by the beans.
Currently it is hard / not possible to override the resource load if the user is using a ClasspathXmlApplicationContext (or any context that does not extend GenericApplicationContext).
Affects: 4.1.6
Issue Links:
Referenced from: commits 0dff782, 37de0b2
0 votes, 7 watchers
The text was updated successfully, but these errors were encountered: