- 23 10月, 2014 3 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12347
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
Issue: SPR-12286
-
- 22 10月, 2014 10 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12191
-
由 Brian Clozel 提交于
During the HTTP Content Negotiation phase, the ContentNegotiationManager uses configured ContentNegotiationStrategy(ies) to define the list of content types accepted by the client. When HTTP clients don't send Accept headers, nor use a configured file extension in the request, nor a request param, developers can define a default content type using the ContentNegotiationConfigurer.defaultContentType() method. This change adds a new overloaded defaultContentType method that takes a ContentNegotiationStrategy as an argument. This strategy will take the current request as an argument and return a default content type. Issue: SPR-12286
-
由 Juergen Hoeller 提交于
Issue: SPR-12334 (cherry picked from commit 6e5711a7)
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12334
-
由 Juergen Hoeller 提交于
Latest dependency updates (EhCache 2.9, Joda-Time 2.5, Jackson 2.4.3, Tiles 3.0.5, Tomcat 8.0.14, FreeMarker 2.3.21)
-
由 Juergen Hoeller 提交于
Consistent throwing of BeanInstantiationException for factory methods, including a hint about circular references Issue: SPR-12317
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
EclipseLinkJpaDialect's getJdbcConnection uses a lazy ConnectionHandle (allowing for deferred internal transaction begin) Issue: SPR-7753
-
- 21 10月, 2014 12 次提交
-
-
由 Andy Clement 提交于
Building on the initial work for SPR-12326, this commit addresses three problems: Firstly the ReflectiveMethodResolver is modified to consider a direct parameter match more important than a varargs match. Also in that same type when there are a number of close matches, the first one is taken rather than the last one. Secondly more testcases and better support have been added for the case of passing a single parameter to a varargs accepting method. Finally it is possible to set the root context object indirectly and not pass it on getValue() calls to the expression objects but not all variants of getValue() were handling that. This is now fixed. Issue: SPR-12326
-
由 Brian Clozel 提交于
This commit adds new htmlEscape methods that take the character encoding as a parameter. According to specs and recommendations, the list of chars to be html escaped depends on the encoding used in the response. If the current char encoding supports chars natively, we shouldn't escape those; of course, reserved chars (<,>,',",&) should always be escaped. See: http://www.w3.org/TR/html4/sgml/entities.html#h-24.3 See: spring-projects/spring-framework#385 by @candrews Issue: SPR-9293
-
由 Stephane Nicoll 提交于
* spr12356: Better use of key iterator
-
由 Min Ho Pak 提交于
This commit uses an EntrySet instead of looping over the keys and retrieving the value in a separate call. Issue: SPR-12356
-
由 Sam Brannen 提交于
When org.junit.Assert.* is statically imported, the class does not compile in Eclipse/STS since XMLAssert extends junit.framework.Assert.
-
由 Sam Brannen 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12299
-
由 Juergen Hoeller 提交于
OrderUtils.getPriority uses AnnotationUtils.findAnnotation for consistent lookup rules and diagnostics Issue: SPR-12357
-
由 Juergen Hoeller 提交于
Issue: SPR-12325
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12352
-
由 Juergen Hoeller 提交于
AnnotationUtils favors local composed annotations over interface annotations and consistently logs introspection failures via lazily initialized logger Issue: SPR-12355 Issue: SPR-12325 Issue: SPR-12329
-
- 20 10月, 2014 4 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12340
-
由 Juergen Hoeller 提交于
Also includes a fix for the Comparable raw type invocation. Issue: SPR-9913 Issue: SPR-12353
-
由 Juergen Hoeller 提交于
Issue: SPR-12351
-
- 18 10月, 2014 4 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12338
-
由 Andy Clement 提交于
The argument processing for compiling constructor references was very basic and this fix removes that and ensures the comprehensive logic written for method argument processing (under SPR-12328) is now used for both method and constructor argument handling. This fixes the reported issue and ensures varargs constructor references can be compiled. This also includes a couple of small fixes for the secondary testcase reported in SPR-12326. The first is to ensure the right root context object is used when it is passed to getValue() indirectly through the evaluation context. The final fix is to ensure correct boxing of primitives is done when a method is called upon a primitive. Issue: SPR-12326
-
由 Rossen Stoyanchev 提交于
This fix addresses a 4.1.1 regression where a raw ResponseEntity return value (used to return potentially a different kind of body) caused an exception. The regression came from the fact we now try to render a null body in order to give ResponseBodyAdvice a chance to substitute a different value. That in turn means we have to try to determine the body type from the method signature. This change improves the logic for extracting the generic parameter type to accommodate a raw ResponseEntity class. Also we avoid raising HttpMediaTypeNotAcceptableException if the value to be rendered is null. Issue: SPR-12287
-
由 Brian Clozel 提交于
-
- 17 10月, 2014 4 次提交
-
-
由 Rossen Stoyanchev 提交于
Commit https://github.com/spring-projects/spring-framework/commit/2b97d6 introduced a change where the path within the DispatcherServlet is determined with each call to ResourceUrlProvider.getForRequestUrl. To avoid repeating that every time a URL is encoded through the response, we now cache the result of the lookupPath determination in ResourceUrlEncodingFilter. Issue: SPR-12332
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
The use of the HandlerMapping.PATH_WITHIN_HANDLER_MAPPING_ATTRIBUTE in ResourceUrlProvider (as a way of saving lookup path determination) leads to incorrect results. For example when the request is forwarded the current requestUri may no longer be compariable to the value of the PATH_WITHIN_HANDLER_MAPPING_ATTRIBUTE. Also where the request is mapped using a pattern, the value of PATH_WITHIN_HANDLER_MAPPING_ATTRIBUTE is not the same as the lookup path. This change removes the use of the attribute from ResourceUrlProvider and instead always determines the lookup path when getForRequestUrl is called. Issue: SPR-12332
-
由 Andy Clement 提交于
This change introduces support for compilation of expressions involving inline lists, string concatenation and method invocations where the method being invoked is declared with a varargs parameter. It also fixes a problem with compiling existing method invocations where the target method is on a non public type. Issue: SPR-12328
-
- 16 10月, 2014 3 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12327
-
由 Juergen Hoeller 提交于
Issue: SPR-12319
-