1. 01 10月, 2013 1 次提交
  2. 27 9月, 2013 1 次提交
  3. 03 9月, 2013 1 次提交
    • R
      Refine destination semantics for msg-handling methods · 0ac6998e
      Rossen Stoyanchev 提交于
      After this change, annotated message handling methods configured to use
      a destination prefix (e.g. "/app") no longer have to include the prefix
      in their mapping. For example if a client sends a message to "/app/foo"
      the annotated methods should be mapped with @MessageMapping("/foo").
      0ac6998e
  4. 29 8月, 2013 1 次提交
  5. 20 8月, 2013 1 次提交
  6. 13 7月, 2013 1 次提交
  7. 31 1月, 2012 1 次提交
    • C
      Rename modules {org.springframework.*=>spring-*} · 02a4473c
      Chris Beams 提交于
      This renaming more intuitively expresses the relationship between
      subprojects and the JAR artifacts they produce.
      
      Tracking history across these renames is possible, but it requires
      use of the --follow flag to `git log`, for example
      
          $ git log spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history up until the renaming event, where
      
          $ git log --follow spring-aop/src/main/java/org/springframework/aop/Advisor.java
      
      will show history for all changes to the file, before and after the
      renaming.
      
      See http://chrisbeams.com/git-diff-across-renamed-directories
      02a4473c
  8. 17 4月, 2010 1 次提交
  9. 30 1月, 2010 2 次提交
    • C
      RESOLVED - issue SPR-6779: imported @Configuration classes do not get enhanced... · fbd797e5
      Chris Beams 提交于
      RESOLVED - issue SPR-6779: imported @Configuration classes do not get enhanced and fail to satisfy scoping requirements
      refactoring, polishing.
      
      fbd797e5
    • C
      IN PROGRESS - issue SPR-6779: imported @Configuration classes do not get... · 110b032a
      Chris Beams 提交于
      IN PROGRESS - issue SPR-6779: imported @Configuration classes do not get enhanced and fail to satisfy scoping requirements
      All tests in ImportedConfigurationClassEnhancementTests now pass.  The fix was simple - imported @Configuration class bean definitions were not getting marked with the attribute that indicates that they are indeed @Configuration class bean definitions.  To make this happen, ConfigurationClassPostProcessor's protected checkConfigurationClassCandidate(beanDef) method is being called from within ConfigurationClassBeanDefinitionReader when imported @Configuration classes are being processed.  This is quick and dirty, and the subsequent check-in will refactor the solution appropriately.
      110b032a
  10. 08 10月, 2009 1 次提交
  11. 21 10月, 2008 1 次提交
  12. 11 7月, 2008 1 次提交