spring-framework

Spring Framework

Rossen Stoyanchev 56c8c69c4c SPR-8642 IMPROVE ERROR REPORTING WHEN RESOLVING MULTIPART REQUEST METHOD ARGUMENTS Separate client from server errors as much as possible in this order: - raise MultipartException when resolving a multipart arg and the request is not a multipart request (400) - raise IllegalArgumentException when the arg type is MultipartFile but the request is not of type MultipartHttpServletRequest (500) - raise MissingServletRequestPartException when a MultipartResolver is in use but the part is not found (400) - detect presence of Servlet 3.0 before using standard multipart parsing to find a request part or raise IllegalArgumentException (500) Unfortunately it is not always possible to separate client from server errors mainly because the Servlet 3.0 API does not distinguish between the case of 0 request parts vs multipart processing not being configured.		15 years ago
..
.settings	ModelAndViewContainer related refinements	15 years ago
src	SPR-8642 IMPROVE ERROR REPORTING WHEN RESOLVING MULTIPART REQUEST METHOD ARGUMENTS	15 years ago
.classpath	[SPR-8222] Upgraded to JUnit 4.9.	15 years ago
.project	adding eclipse project settings	18 years ago
build.xml	+ upgrade to AspectJ 1.6.8	16 years ago
ivy.xml	moved OpenSessionInViewTests back to orm module	15 years ago
pom.xml	Update Servlet 3.0 dependency in webmvc pom	15 years ago
template.mf	mvc:annotation-driven reliably detects JSR-303 and JAXB2 in an OSGi environment as well (SPR-7291)	16 years ago
web-servlet.iml	moved OpenSessionInViewTests back to orm module	15 years ago