Closed fabapp2 closed 2 years ago
CommonsMultipartResolver
Deprecation part is not done, possible partial implementation for SecurityManager
Deprecation
Anyone knows what is recommended to use instead of CommonsMultipartResolver
? Other than having a TODO
comment over the corresponding bean definition i have no idea what to do...
Hi @BoykoAlex, the API states
The common alternative is
StandardServletMultipartResolver
, delegating to the Servlet container's own multipart parser, with configuration to happen at the container level and potentially with container-specific limitations.
Not sure what this means for the recipe though.
CommonsMultipartResolver
Deprecation part is not done, possible partial implementation forSecurityManager
Deprecation
@sanagaraj-pivotal where to find it?
@BoykoAlex I clarified with the team, see my updated description.
Can anyone tell me about the alternative solution for CommonsMultipartResolver? I have this bean in my project, and I need to replace after I upgraded the spring-web dependency.
https://github.com/spring-projects/spring-boot/wiki/Spring-Boot-3.0.0-M1-Release-Notes#miscellaneous
What needs to be done
SecurityManager
is used?CommonsMultipartResolver
is used?SecurityManager
Finder
Find
System.getSecurityManager()
orAccessControlException
(potential contribution)Implementation
Recipe
None
Report
Inform the user about the potential usage of
SecurityManager
and that this class was removed.CommonsMultipartResolver
Finder
Find bean definitions of type
CommonsMultipartResolver
Implementation
ProjectResourceFinder
delegating to the recipe to find Spring bean declarations by type using theProjectContext
Recipe
Remove beans of type
CommonsMultipartResolver
Implementation
RemoveCommonsMultipartResolverBeanDeclarations
that uses the finder and removes bean declaration methods (potential contribution)Report
Suggest to remove
CommonsMultipartResolver
bean and relying on Spring Boot auto-configuration