- 30 4月, 2014 8 次提交
-
-
由 Sebastien Deleuze 提交于
DestinationCache is now used for both plain and pattern destinations. It stores internally the subscriptions map for each cached destination. Subscriptions are initially created when there is no cache for the requested destination, and are updated when subscriptions change. Issue: SPR-11657
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Avoid dependency on order in which expected messages are received.
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
This change simplifies the implementation of the "test" EventPublisher and MessageHandler used in the STOMP broker relay integration tests. The updated implementations use a time-limted poll on a BlockingQueue.
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
AbstractAutoProxyCreator and AbstractAdvisingBeanPostProcessor consistently not considering configuration callbacks and internal language interfaces as reasonable proxy interfaces Issue: SPR-11715
-
- 29 4月, 2014 10 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
AbstractAdvisingBeanPostProcessor uses target class check for existing proxy but checks against actual exposed object otherwise (catching introductions) Issue: SPR-11725
-
由 Rossen Stoyanchev 提交于
-
由 Chexpir 提交于
-
由 Sebastien Deleuze 提交于
Also update <mvc:annotation-driven /> comment in XSD. Issue: SPR-11703
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11672
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Revised @PropertySource parsing for consistent PropertySource naming, avoiding accidental overriding by name Issue: SPR-11637
-
由 Juergen Hoeller 提交于
Issue: SPR-9335
-
由 Juergen Hoeller 提交于
Issue: SPR-11647
-
- 28 4月, 2014 7 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10744
-
由 Juergen Hoeller 提交于
Issue: SPR-9671
-
由 Juergen Hoeller 提交于
(cherry picked from commit c97c2469)
-
由 Juergen Hoeller 提交于
Issue: SPR-11737 (cherry picked from commit 93d13cfc) (cherry picked from commit 4196e6c9)
-
由 Juergen Hoeller 提交于
Issue: SPR-11721 (cherry picked from commit 59cef3ce)
-
由 Juergen Hoeller 提交于
Configuration class processing explicitly skips java.* classes since we'll never find @Bean annotations there anyway Issue: SPR-11718 (cherry picked from commit c8ea80d7)
-
由 Juergen Hoeller 提交于
@Bean processing explicitly ignores bridge methods (for method overrides with return type narrowing on JDK 8) Issue: SPR-11718 (cherry picked from commit 656fc52f)
-
- 26 4月, 2014 4 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Also respect HandlerMapping order in ResourceUrlProvider
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
The original fix for SPR-11423: https://github.com/spring-projects/spring-framework/commit/32e5f57e647022d9ea82c03670936bf31f8467de was insufficient when using an external broker since the original destination header has to be in the "native headers" map (i.e. with STOMP headers) in order to be included in messages broadcast by the broker.
-
- 25 4月, 2014 4 次提交
-
-
由 Brian Clozel 提交于
The ResourceResolverChain can return null, so PrefixResourceResolver should be skipped in that case.
-
由 Stephane Nicoll 提交于
* pull530: Add space separator in JsonPathExpectationsHelper
-
由 Alex Panchenko 提交于
-
由 Rossen Stoyanchev 提交于
-
- 24 4月, 2014 7 次提交
-
-
由 Stephane Nicoll 提交于
This commit removes the queue attribute of the JmsListener annotation as this information should be provided by the container factory and not by each individual listener endpoints. There was a side effect that an annotation value cannot be null, which was forcing the container to be a queue-based container by default. Issue: SPR-9882
-
由 Brian Clozel 提交于
The configured prefix should not begin with a "/", since PublicResourceUrlProvider is already taking path mapping into account when resolving resources and URLs.
-
由 Stephane Nicoll 提交于
This commit replaces the "responseDestination" attribute on the JmsListener annotation by a support of the standard SendTo annotation. Issue: SPR-11707
-
由 Stephane Nicoll 提交于
Prior to this commit, the default JmsListenerContainerFactory to use must be explicitly set. Since having a single container factory is a fairly common use case, we look up the default one automatically using the bean name "jmsListenerContainerFactory". It is still possible to provide an explicit default but since it refers more to "the" container factory to use, the parameter has been renamed to "containerFactory" which is shorter and more explicit. The lookup strategy is lazy: if all endpoints are providing an explicit container factory and no container factory with the "jmsListenerContainerFactory" bean name exists, no exception will be thrown. Issue : SPR-11706
-
由 Rossen Stoyanchev 提交于
This change modifies the names of the Reactor support classes in order to align with the same changes in the 4.0.x line which now supports both Reactor 1.1 and 1.0. Issue: SPR-11636
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11721
-