- 12 9月, 2014 3 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12182
-
由 Juergen Hoeller 提交于
Issue: SPR-12173
-
由 Juergen Hoeller 提交于
Issue: SPR-12174 Issue: SPR-12157
-
- 10 9月, 2014 3 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12171
-
由 Sam Brannen 提交于
Per the Javadoc for the SocketUtils() constructor, SocketUtils can be instantiated as a Spring Bean in XML configuration files; however, SocketUtils is currently abstract which prevents such usage. This commit removes the 'abstract' declaration thereby allowing SocketUtils to be instantiated as a Spring bean. Issue: SPR-12169
-
- 08 9月, 2014 2 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12157
-
- 06 9月, 2014 1 次提交
-
-
由 Brian Clozel 提交于
Prior to this change, getForRequestUrl implementation would only work for applications with a non-empty servlet path. So web applications mapped to "/" would trigger a IllegalStateException while checking the current request against the request path within the current mapping. This change relaxes this and only check that the path within mapping is within the request URL. Issue: SPR-12158
-
- 05 9月, 2014 2 次提交
-
-
由 Sebastien Deleuze 提交于
This commit also fixes the AbstractMappingJacksonResponseBodyAdvice Javadoc. Issue: SPR-12149
-
由 Juergen Hoeller 提交于
Issue: SPR-12151
-
- 04 9月, 2014 17 次提交
-
-
由 Spring Buildmaster 提交于
-
由 Sebastien Deleuze 提交于
Issue: SPR-12149
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Dropped RequestEntity's template variable methods in order to remove dependencies on org.springframework.web Instead, as outlined in the revised javadoc, let's recommend manual UriTemplate usage for RequestEntity URI input. Issue: SPR-11752
-
由 Brian Clozel 提交于
This change moves the resource-cache configuration to the <resource-chain/> tag, since enabling/disabling resource cache should be driven by a property or a SpEL expression. So now that configuration can be set with XML attributes: <mvc:resource-chain resource-cache="true" cache-manager="resourceCache" cache-name="test-resource-cache"> In order to mirror the JavaConfig behavior, the "resource-cache" attribute is required. Issue: SPR-12129
-
由 Rossen Stoyanchev 提交于
Issue: SPR-14036
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11870
-
由 Rossen Stoyanchev 提交于
Before this change ResourceUrlProvider used getUrlMap to detect ResourceHttpRequestHandler instances, however the map may contain bean names as is the case when using <mvc:resources>. Instead it now uses getHandlerMap.
-
由 Rossen Stoyanchev 提交于
This change adds a ResourceUrlProvider bean to the ResourceBeanDefinitionParser to match the same in the Java config. For consistency the name of the bean in the Java config is renamed. Also a ResourceUrlProviderExposingInterceptor is declares as a global MappedInterceptor.
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11310 Issue: SPR-10548
-
由 Juergen Hoeller 提交于
Issue: SPR-12148
-
由 Juergen Hoeller 提交于
Issue: SPR-12141
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
- 03 9月, 2014 12 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-12145
-
由 Juergen Hoeller 提交于
ImportRegistry as a package-visible top-level interface which can easily be shared within the package Issue: SPR-12128
-
由 Brian Clozel 提交于
Prior to this change, ResourceTransformers that transformed resources by updating the links to other resources, worked only if links were relative to the resource being transformed. For example, when the CssLinkResourceTransformer rewrote links within a "main.css" resource, only links such as "../css/other.css" were rewritten. Using relative links is a recommended approach, because it's totally independent from the application servlet path, context path, mappings... This change allows absolute links to be rewritten by those Transformers, provided those links are accurate and point to existing resources. Issue: SPR-12137
-
由 Sebastien Deleuze 提交于
Issue: SPR-12113
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Phillip Webb 提交于
Update ImportRegistry to track all import registrations that occur against an importing class (rather than just keeping the last). In addition, prune imported classes from the registry when a configuration class is removed during the REGISTER_BEAN ConfigurationPhase. This update prevents incorrect metadata from being injected into an ImportAware class which is imported twice by different configurations classes (when one of the configuration classes will be ultimately skipped due to a @Condition). Issue: SPR-12128
-
由 Andy Clement 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
AbstractAutowireCapableBeanFactory avoids early FactoryBean instantiation on currently created configuration bean Issue: SPR-12141
-
由 Sam Brannen 提交于
-