1. 09 11月, 2013 1 次提交
  2. 08 11月, 2013 3 次提交
    • R
      Simplify determination of SockJS path · 2a6c1f75
      Rossen Stoyanchev 提交于
      The SockJS path is now passed to the SockJsService handleRequest method
      thus removing the need to guess it.
      
      Issue: SPR-11058
      2a6c1f75
    • R
      Return AbstractSubscribableChannel from @Bean methods · 6a18daea
      Rossen Stoyanchev 提交于
      Declare SubscribableChannel @Beans in
      WebSocketMessageBrokerConfigurationSupport as
      AbstractSubscribableChannel to avoid the need for casting when
      registering interceptors.
      
      Issue: SPR-11065
      6a18daea
    • R
      Update user destinations handling · 0340cc5f
      Rossen Stoyanchev 提交于
      Before this change subscribing to a user-specific destination in STOMP
      required manually appending a unique queue suffix provided in a header
      with the CONNECTED frame.
      
      This change removes the need to do that. Instead STOMP clients can
      subscribe to "/user/queue/error" and can then begin to receive messages
      sent to "/user/{username}/queue/error" without colliding with any other
      user doing the same.
      
      Issue: SPR-11077
      0340cc5f
  3. 07 11月, 2013 1 次提交
    • S
      Use AsciiDoctor special characters · c09f8517
      Sam Brannen 提交于
       - Replaced ellipsis with "..."
      
       - Replaced em dash with "--"
      
       - Fixed issue with italics migration in the Standard Annotation Support
        section of the Testing chapter
      c09f8517
  4. 06 11月, 2013 9 次提交
  5. 05 11月, 2013 12 次提交
  6. 04 11月, 2013 2 次提交
    • J
      Added get(key, type) method to Cache interface · 50d3f719
      Juergen Hoeller 提交于
      This new get variant not only allows for generically specifying the required value type; it also skips the ValueWrapper that the standard get method returns. Note that it is not possible to differentiate between non-existing cache entries and cached null values that way; for that purpose, the standard get variant needs to be used.
      
      Issue: SPR-11061
      50d3f719
    • J
      Use non-lenient constructor resolution mode for @Bean methods · b093b849
      Juergen Hoeller 提交于
      Since @Bean methods are never used with externally specified constructor argument values but rather just with autowiring, the non-lenient constructor resolution mode is appropriate in case of an overloaded @Bean method, not performing any type difference weight checks. This change includes a refinement of Spring's existing non-lenient constructor resolution (which needs to be explicitly turned on and is therefore not well tested), narrowing the conditions for the ambiguity check (only in case of the same number of arguments and not for overridden methods).
      
      Issue: SPR-10988
      b093b849
  7. 03 11月, 2013 1 次提交
  8. 02 11月, 2013 6 次提交
  9. 01 11月, 2013 2 次提交
  10. 31 10月, 2013 3 次提交