- 19 10月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
Restore the ability to create a TypeDescriptor for a collection or map where the generics may be null. Issue: SPR-11006
-
- 18 10月, 2013 2 次提交
-
-
由 Phillip Webb 提交于
Refactor TypeDescriptor to use ResolvableType in order to retain full generic type information, in the process fixing MultiValueMap support in MapToMapConverter. Issue: SPR-9499
-
由 Phillip Webb 提交于
Fix 'missing serialVersionUID' warnings, support for void.class types and refine resolve() algorithm to support narrowed types. Issue: SPR-10973
-
- 17 10月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
- Support for serialization - Allow programmatic creation of an array from a given component type - Allow programmatic creation with given generics - Extract generics from Class types using Class.getTypeParameters() - Move TypeVariableResolver to an inner class (and make method private) - Refine 'resolve()' algorithm Issue: SPR-10973
-
- 15 10月, 2013 5 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
- Now avoiding NullPointerExceptions in GenericTypeResolver's resolveReturnTypeForGenericMethod() in case the supplied ClassLoader is null. - AutowireUtils.resolveReturnTypeForFactoryMethod() now properly asserts that the supplied ClassLoader is not null. - Fixed copy-n-paste errors in Javadoc for AutowireUtils.resolveReturnTypeForFactoryMethod(). Issue: SPR-10411
-
由 Sam Brannen 提交于
SPR-10411
-
由 Juergen Hoeller 提交于
Includes revisions of MethodParameter and DependencyDescriptor (in particular towards a reference to the containing class). Also refines several ResolvableType method signatures. Issue: SPR-9965
-
由 Juergen Hoeller 提交于
We're consistently resolving class names now, and the entire algorithm moved from GenericTypeResolver to the internal AutowireUtils helper in the bean factory package. Issue: SPR-10411
-
- 14 10月, 2013 1 次提交
-
-
由 Sam Brannen 提交于
-
- 11 10月, 2013 2 次提交
-
-
由 Phillip Webb 提交于
Issue: SPR-10973
-
由 Phillip Webb 提交于
Fix ResolvableType.isAssignableFrom to correctly deal with <?> style generics. Issue: SPR-10973
-
- 10 10月, 2013 4 次提交
-
-
由 Phillip Webb 提交于
Refactor AbstractMessageConverterMethodArgumentResolver and BridgeMethodResolver to use ResolvableType in preference to deprecated GenericTypeResolver calls. Issue: SPR-10980
-
由 Phillip Webb 提交于
Refactor GenericCollectionTypeResolver to make use of ResolvableType for generic resolution. Issue: SPR-10977
-
由 Phillip Webb 提交于
Refactor GenericTypeResolver to make use of ResolvableType for generic resolution. Issue: SPR-10978
-
由 Phillip Webb 提交于
Add a new ResolvableType Class which encapsulates java.lang.reflect.Type, providing access to supertypes, interfaces and generic parameters along with the ability to ultimately resolve to a java.lang.Class. ResolvableTypes may be obtained from fields, method parameters, method returns, classes or directly from a java.lang.reflect.Type. Most methods will themselves return ResolvableTypes, allowing easy navigation. For example: private HashMap<Integer, List<String>> myMap; public void example() { ResolvableType t = ResolvableType.forField( getClass().getDeclaredField("myMap")); t.getSuperType(); // AbstractMap<Integer, List<String>>; t.asMap(); // Map<Integer, List<String>> t.getGeneric(0).resolve(); // Integer t.getGeneric(1).resolve(); // List t.getGeneric(1); // List<String> t.resolveGeneric(1, 0); // String } Issue: SPR-10973
-
- 05 10月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
Comprehensive update to the framework's TimeZone handling, including a new TimeZoneAwareLocaleContext and a LocaleContextResolver for Spring MVC A few noteworthy minor changes: LocaleContext.getLocale() may return null in special cases (not by default), which our own accessing classes are able to handle now. If there is a non-null TimeZone user setting, we're exposing it to all collaborating libraries, in particular to JSTL, Velocity and JasperReports. Our JSR-310 and Joda-Time support falls back to checking the general LocaleContext TimeZone now, adapting it to their time zone types, if no more specific setting has been provided. Our DefaultConversionService has TimeZone<->ZoneId converters registered. And finally, we're using a custom parseTimeZoneString method now that doesn't accept the TimeZone.getTimeZone(String) GMT fallback for an invalid time zone id anymore. Issue: SPR-1528
-
由 Juergen Hoeller 提交于
-
- 28 9月, 2013 1 次提交
-
-
由 Phillip Webb 提交于
Fix ASM AnnotationAttributesReadingVisitor to correctly deal with subclasses enums. Issue: SPR-10914
-
- 14 9月, 2013 1 次提交
-
-
由 Rob Winch 提交于
Added test to StandardReflectionParameterNameDiscoverer that demonstrates discovering of parameter names on an interface. Issue: SPR-9643
-
- 12 9月, 2013 1 次提交
-
-
由 Sam Brannen 提交于
-
- 04 9月, 2013 1 次提交
-
-
由 Arjen Poutsma 提交于
Added extension to Future with capabilities for registering callbacks when the future is complete. - Added ListenableFuture, ListenableFutureCallback, ListenableFutureCallbackRegistry, and ListenableFutureTask. - Using ListenableFuture in AsyncRestOperations/AsyncRestTemplate. - Added AsyncListenableTaskExecutor, implemented in SimpleAsyncTaskExecutor. - Added FutureAdapter and ListenableFutureAdapter.
-
- 30 8月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-1528
-
- 29 8月, 2013 3 次提交
-
-
由 Antonio Marrero 提交于
Update AntPathMatcher Comparator to treat `/**` in the same way as `null` paths. Prior to this commit the pattern `/**` would be picked in preference to patterns with 3 or more PathVariable (e.g. `/matches/{matchId}/ periods/{periodId}/teams/{teamId}/results`). Issue: SPR-10550
-
由 Phillip Webb 提交于
Refine AntPathMatcher.combine rules to allow direct concatenation of patterns when pattern1 does not contain '*.'. Prior to this commit direct concatenation was allowed when pattern1 did not contain '.', this prevented calls of the form: pathMatcher.combine("/1.0", "/foo/test") from working as expected. This commit also applies some general cleanup to the `combine` method. Issue: SPR-10554
-
由 Juergen Hoeller 提交于
-
- 28 8月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
This turned into a rather huge affair since it led to the introduction of a new AutowireCandidateResolver implementation in the spring-context module. That ACR impl is now being set through AnnotationConfigUtils; GenericApplicationContext and co do not set a default QualifierAnnotationAutowireCandidateResolver anymore (which has always been a smell anyway). At the same time, dependency ordering has moved from AutowiredAnnotationBeanPostProcessor to DefaultListableBeanFactory itself through a "dependencyComparator" strategy, applying to constructor dependencies and lazy resolution proxies as well. Issue: SPR-10353
-
- 27 8月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
-
- 23 8月, 2013 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Issue: SPR-8738
-
- 22 8月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-5574
-
- 21 8月, 2013 3 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10181
-
由 Juergen Hoeller 提交于
Issue: SPR-10181
-
由 Juergen Hoeller 提交于
Issue: SPR-10819
-
- 08 8月, 2013 2 次提交
-
-
由 Juergen Hoeller 提交于
Introduced DefaultParameterNameDiscoverer which checks JDK 8's standard reflection first and then falls back to ASM-based debug symbol analysis Also, StandardReflectionParameterNameDiscoverer calls "Parameter.isNamePresent()" now to return null (and pass on to the next discoverer) if no JDK 8 parameters are available. Note that this requires OpenJDK 8 b100 or higher to compile now. Issue: SPR-10532
-
由 Rossen Stoyanchev 提交于
MimeType is available in core-spring and does not include support for quality parameters and media used in HTTP content negotiation. The MediaType sub-class in org.springframework.http adds q-parameters.
-
- 03 8月, 2013 2 次提交
-
-
由 Rossen Stoyanchev 提交于
See javadoc in SockJsService for details. Also remove ReadOnlyMultiValueMap, CollectionUtils has a method for that already.
-
由 Rossen Stoyanchev 提交于
The method returning query parameters now returns only query string parameters as opposed to any Servlet request parameter. This commit also adds a ReadOnlyMultiValueMap.
-
- 01 8月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10767 (cherry picked from commit d0948f1f)
-
- 31 7月, 2013 1 次提交
-
-
由 Juergen Hoeller 提交于
PropertySourcesPlaceholderConfigurer's "ignoreUnresolvablePlaceholders" setting reliably applies to nested placeholders as well Issue: SPR-10549
-