- 02 3月, 2013 6 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-10339
-
由 Juergen Hoeller 提交于
Issue: SPR-10339
-
由 Phillip Webb 提交于
# By Jakub Narloch * SPR-8509: Add Castor XSD information to reference docs
-
由 Jakub Narloch 提交于
Update the Spring OXM reference documentation to include changes introduced in CastorMarshaller, specifically around CastorMarshaller XSD configuration. Issue: SPR-8509
-
由 Phillip Webb 提交于
Refactor FrameworkServlet.doOptions() to capture the "Allow" header by using a HttpServletResponseWrapper. Prior to this commit the HttpServletResponse.getHeader() method was used which is only available in Servlet 3.0 environments. Issue: SPR-10341
-
- 01 3月, 2013 9 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-10335
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Also mentioning JDBC 4's unwrap method for obtaining the native connection now. Issue: SPR-10312
-
由 Juergen Hoeller 提交于
GroovyScriptFactoryTests passes again now. Issue: SPR-10304
-
由 Phillip Webb 提交于
# By Carson McDonald * fix-typos-3: Fix minor javadoc typos
-
由 Carson McDonald 提交于
-
由 Phillip Webb 提交于
# By Tomasz Nurkiewicz * patch-1: Fix incorrect closing <web-app> tag in MVC docs
-
由 Tomasz Nurkiewicz 提交于
-
由 Phillip Webb 提交于
Issue: SPR-10210
-
- 28 2月, 2013 9 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
Now invoking JdbcTemplate's queryForObject() method instead of the deprecated queryForInt() method within the test suite. Issue: SPR-10257
-
由 Chris Beams 提交于
Issue: SPR-10208
-
由 Sam Brannen 提交于
JdbcTestUtils now invokes JdbcTemplate's queryForObject() method instead of the deprecated queryForInt() method. Issue: SPR-10257
-
由 Sam Brannen 提交于
Issue: SPR-10333
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
JdbcTestUtils now invokes JdbcTemplate's queryForObject() method instead of the deprecated queryForInt() method. Issue: SPR-10257
-
由 Phillip Webb 提交于
Inner beans are not prototype beans as, in contrast to what is documented in the section for prototype beans, the inner bean does get destruction callbacks applied. Issue: SPR-10311
-
- 27 2月, 2013 7 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-10282
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-10301
-
由 Juergen Hoeller 提交于
Issue: SPR-10323
-
由 Phillip Webb 提交于
-
- 26 2月, 2013 9 次提交
-
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
This commit introduces TestGroup#JMXMP and adds assumptions to related tests accordingly. These tests require the jmxoptional_remote jar on the classpath, and are run nightly in the SPR-PERF build. Issue: SPR-8089
-
由 Chris Beams 提交于
This commit lays the groundwork for introducing TestGroup#JMXMP and related assumptions in select JMX-related tests in a subsequent commit; JUnit assumptions require JUnit 4+ to function properly, so the entire AbstractMBeanServerTests hierarchy must be moved over to JUnit 4+ style. Issue: SPR-8089
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
This reverts commit cc814519. Issue: SPR-8089 Conflicts: spring-context/src/test/java/org/springframework/jmx/access/RemoteMBeanClientInterceptorTestsIgnore.java spring-context/src/test/java/org/springframework/jmx/support/ConnectorServerFactoryBeanTestsIgnore.java
-
由 Chris Beams 提交于
-
由 Chris Beams 提交于
Issue: SPR-10074, SPR-10333
-
由 Chris Beams 提交于
These tests still fail under Eclipse for unknown reasons, but do work under Gradle, so are thus re-enabled by removing the @Ignore. Issue: SPR-10074
-
由 Chris Beams 提交于
Prior to this change, CallbacksSecurityTests#testContainerPrivileges was @Ignored because it caused the build to fail under Gradle. After some analysis, the root cause was determined to be the fact that (a) a restrictive SecurityManager is active during the running of this test, and (b), Gradle intercepts System.out and routes it through its internal LogBack-based logging system. LogBack requires a call to Class#getClassLoader when handling logging statements, and the SecurityManager disallows this call, thus raising the error that fails the build. This commit solves the problem by eliminating the System.out.println call in question and removing the @Ignore annotation from the test. The console output was diagnostic in nature anyway, and not required for the successful execution of the test's assertions. Issue: SPR-10074
-