1. 06 7月, 2016 1 次提交
  2. 05 7月, 2016 1 次提交
  3. 03 6月, 2016 1 次提交
  4. 22 7月, 2015 1 次提交
  5. 02 6月, 2015 1 次提交
  6. 10 5月, 2015 1 次提交
  7. 09 5月, 2015 1 次提交
  8. 08 2月, 2014 1 次提交
  9. 29 1月, 2014 1 次提交
  10. 28 1月, 2014 2 次提交
    • S
      Polish Hibernate support and tests · 63e02317
      Sam Brannen 提交于
       - Fix Javadoc in HibernateTemplate so that it compiles in Eclipse.
       - Suppress generics warnings in HibernateTemplateTests.
       - Remove unnecessary deprecation warning suppression in constructor for
         LocalSessionFactoryBuilder.
      63e02317
    • J
      Introduced HibernateTemplate for Hibernate 4 as a migration helper · 79e17dbf
      Juergen Hoeller 提交于
      Note that this variant of HibernateTemplate is stripped down in terms of Session management options and just provides a current-session style with a fallback to a temporary session-per-operation.  Furthermore, in the latter fallback mode, only read operations are supported, just like with a JPA EntityManager.
      
      Issue: SPR-11291
      79e17dbf
  11. 26 11月, 2013 1 次提交
    • P
      Fix remaining compiler warnings · 59002f24
      Phillip Webb 提交于
      Fix remaining Java compiler warnings, mainly around missing
      generics or deprecated code.
      
      Also add the `-Werror` compiler option to ensure that any future
      warnings will fail the build.
      
      Issue: SPR-11064
      59002f24
  12. 14 5月, 2013 1 次提交
  13. 29 3月, 2013 1 次提交
  14. 02 1月, 2013 1 次提交
  15. 29 12月, 2012 3 次提交
  16. 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
  17. 09 10月, 2011 1 次提交
    • C
      Revert "Introduce (Annotation)SessionFactoryBuilder types" · 3bb01ee6
      Chris Beams 提交于
      This commit and the several before it back out the
      SessionFactoryBuilder and AnnotationSessionFactoryBuilder types
      recently introduced in 3.1 M2. This is in light of the impending
      release of Hibernate 4.0 GA and our own support for it the new
      org.springframework.orm.hibernate4 package (not yet committed).
      
      This new package will have a similar, but far simpler, arrangement of
      a single LocalSessionFactoryBuilder and LocalSessionFactoryBean pair.
      Hibernate 3.x support will remain largely as-is, however the
      HibernateTransactionManager introduced with SPR-8076 will remain.
      
      This reverts commit 9e8259198f07e495fd32359c0e0c197bb79a2ca0.
      
      Issue: SPR-8066, SPR-7936, SPR-8076, SPR-8098, SPR-8096, SPR-7387
      3bb01ee6
  18. 31 3月, 2011 1 次提交
    • C
      Introduce (Annotation)SessionFactoryBuilder types · f5768fe0
      Chris Beams 提交于
      Large refactoring of existing *SessionFactoryBean hierarchy designed to
      support configuration of Hibernate SessionFactory objects within
      @Configuration class @Bean methods without forcing use of a
      FactoryBean type, which is generally discouraged due to awkwardness
      of programming model and lifecycle issues.  Refactored and new types
      include:
      
          * Removal of AbstractSessionFactoryBean, replacing it with
            SessionFactoryBeanSupport abstract base class
      
          * Introduction of SessionFactoryBuilder and
            AnnotationSessionFactoryBuilder types, both direct subclasses of
            SessionFactoryBuilderSupport. These types are intended for direct
            use within @Bean methods. They expose method-chainable set*
            methods allowing for concise and convenient use. See JavaDoc
            on both types for usage examples.
      
          * LocalSessionFactoryBean and AnnotationSessionFactoryBean types are
            now subclasses, respectively, of the *Builder types above.
      
      LSFB and ASFB backward-compatibility has been maintained almost
      entirely. The one exception is that there is no longer a protected
      convertHibernateAccessException() method available in the hierarchy.
      This method was not likely often used anyway and has been replaced
      by the new (and public) setPersistenceExceptionTranslator() which
      accepts instances of type HibernateExceptionTranslator as introduced in
      SPR-8076.
      
      LSFB and ASFB setter method signatures have changed. They no longer
      return void in standard JavaBeans style but rather, and due to extending
      the *Builder types above, return the 'this' reference. This posed a
      problem because the Spring container has to date been unable to detect
      and provide dependency injection against non-void returning setter
      methods. This limitation was due to the way that the default JavaBeans
      Introspector class and its getBeanInfo() method works, and prompted the
      introduction and intergration of ExtendedBeanInfo, already completed in
      SPR-8079. So have no concern if you notice this signature change - it
      all works.
      
      Certain deprecations have been made:
      
          * All LSFB/ASFB methods related to Hibernate's CacheProvider SPI,
            reflecting its deprecation in Hibernate 3.3 in favor of the new
            RegionFactory SPI. Note these methods have been preserved only
            on the FactoryBean types. The new *SessionFactoryBuilder
            supertypes do not expose CacheProvider services at all.
      
          * All protected LSFB/ASFB methods that accept a Hibernate
            Configuration parameter, such as newSessionFactory(Configuration),
            postProcessMappings(Configuration) and
            postProcessConfiguration(Configuation), in favor of no-arg methods
            with the same names. Due to the nature of the hierarchy
            refactoring mentioned above, the Configuration instance is always
            available when these methods are called, thus no need to pass it
            in as a parameter.
      
      In the process, our approach to automatic detection of Hibernate dialect
      has been improved (it was in fact broken before). Thanks to James
      Roper for his suggestion in SPR-7936 as to how to fix this.
      
      See HibernateSessionFactoryConfigurationTests as a starting point for
      understanding the new builder-style approach to SessionFactory creation.
      Note especially use of the SessionFactoryBuilder#doWithConfiguration
      method which allows for direct programmatic configuration of the Native
      Hibernate (Annotation)Configuration API.
      
      As a final note, AnnotationConfiguration has been deprecated in
      Hibernate 3.6, and great pains have been taken to ensure that users
      of any supported Hibernate version (3.2 -> 3.6) will never need to
      (a) cast from Configuration to AnnotationConfiguration or (b)
      experience deprecation warnings due to being forced to use the
      AnnotationConfiguration API. Explore the JavaDoc around the
      doWithConfiguration() method and HibernateConfigurationCallback type
      for complete details.
      
      Issue: SPR-8066, SPR-7936, SPR-8076, SPR-8098
      f5768fe0
  19. 19 2月, 2009 1 次提交
  20. 26 1月, 2009 1 次提交
  21. 28 11月, 2008 1 次提交
  22. 27 11月, 2008 1 次提交
  23. 28 10月, 2008 1 次提交
  24. 24 10月, 2008 1 次提交