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
{{ message }}
This repository has been archived by the owner on Jan 19, 2022. It is now read-only.
Sample
For additional context we have a feature that allows our users to build solutions that are multi-tenanted. Where the application context can be configured with multiple resourceloader instances. Each with its own instance of the SimpleStorageProtocolResolver with, in turn, its own configured AmazonS3 bean.
This piece of code would seem to indicate that the implementation now assumes that there will only ever be a single AmazonS3 bean in the application context.
The text was updated successfully, but these errors were encountered:
paulcwarren
changed the title
SimpleStorageProtocolResovler constructor no longer visible
SimpleStorageProtocolResolver constructor no longer visible
Nov 23, 2020
Type: Bug
Component:
S3
Describe the bug
We relied on the public constructor that used to accept an AmazonS3 client but is not longer visible. Therefore we were broken when we upgraded from Hoxton.SR8 TO SR9.
Sample
For additional context we have a feature that allows our users to build solutions that are multi-tenanted. Where the application context can be configured with multiple resourceloader instances. Each with its own instance of the
SimpleStorageProtocolResolver
with, in turn, its own configured AmazonS3 bean.This piece of code would seem to indicate that the implementation now assumes that there will only ever be a single AmazonS3 bean in the application context.
The text was updated successfully, but these errors were encountered: