- 27 11月, 2013 2 次提交
-
-
由 Sam Brannen 提交于
Prior to this commit, the Spring TestContext Framework (TCF) supported the use of test-related annotations as meta-annotations for composing custom test stereotype annotations; however, attributes in custom stereotypes could not be used to override meta-annotation attributes. This commit addresses this by allowing attributes from the following annotations (when used as meta-annotations) to be overridden in custom stereotypes. - @ContextConfiguration - @ActiveProfiles - @DirtiesContext - @TransactionConfiguration - @Timed - @TestExecutionListeners This support depends on functionality provided by AnnotatedElementUtils. See the 'Notes' below for further details and ramifications. Notes: - AnnotatedElementUtils does not support overrides for the 'value' attribute of an annotation. It is therefore not possible or not feasible to support meta-annotation attribute overrides for some test-related annotations. - @ContextHierarchy, @WebAppConfiguration, @Rollback, @Repeat, and @ProfileValueSourceConfiguration define single 'value' attributes which cannot be overridden via Spring's meta-annotation attribute support. - Although @IfProfileValue has 'values' and 'name' attributes, the typical usage scenario involves the 'value' attribute which is not supported for meta-annotation attribute overrides. Furthermore, 'name' and 'values' are so generic that it is deemed unfeasible to provide meta-annotation attribute override support for these. - @BeforeTransaction and @AfterTransaction do not define any attributes that can be overridden. - Support for meta-annotation attribute overrides for @Transactional is provided indirectly via SpringTransactionAnnotationParser. Implementation Details: - MetaAnnotationUtils.AnnotationDescriptor now provides access to the AnnotationAttributes for the described annotation. - MetaAnnotationUtils.AnnotationDescriptor now provides access to the root declaring class as well as the declaring class. - ContextLoaderUtils now retrieves AnnotationAttributes from AnnotationDescriptor to look up annotation attributes for @ContextConfiguration and @ActiveProfiles. - ContextConfigurationAttributes now provides a constructor to have its attributes sourced from an instance of AnnotationAttributes. - ContextLoaderUtils.resolveContextHierarchyAttributes() now throws an IllegalStateException if no class in the class hierarchy declares @ContextHierarchy. - TransactionalTestExecutionListener now uses AnnotatedElementUtils to look up annotation attributes for @TransactionConfiguration. - Implemented missing unit tests for @Rollback resolution in TransactionalTestExecutionListener. - SpringJUnit4ClassRunner now uses AnnotatedElementUtils to look up annotation attributes for @Timed. - TestContextManager now retrieves AnnotationAttributes from AnnotationDescriptor to look up annotation attributes for @TestExecutionListeners. - DirtiesContextTestExecutionListener now uses AnnotatedElementUtils to look up annotation attributes for @DirtiesContext. Issue: SPR-11038
-
由 Phillip Webb 提交于
Delete the unused GlassFishLoadTimeWeaverTests and in the process fix the "Unable to load JUnit4 runner to calculate Ignored test cases" Gradle error. Issue: SPR-10563
-
- 26 11月, 2013 11 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11105
-
由 Rossen Stoyanchev 提交于
This change fixes a timing issue in tests using Spring MVC Tests where assertions on an async result may not wait long enough. The fix involves the use of a new callback in MockAsyncContext that allows tests to detect when an async dispatch has been invoked. Issue: SPR-10838
-
由 Rossen Stoyanchev 提交于
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
@Rollback now supports ANNOTATION_TYPE as a target, allowing it to be used as meta-annotation. Note: this change was accidentally omitted from the original commit for SPR-7827. Issue: SPR-7827
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Phillip Webb 提交于
* doc-typos: Fix various typos
-
由 Eric Dahl 提交于
Fix a variety of typos throughout the project, primarily in comments (javadoc or otherwise) but also in a handful of log messages and a couple exception messages. ISSUE: SPR-11123
-
由 Rossen Stoyanchev 提交于
The addition of SubProtocolCapable simplifies configuration since it is no longer necessary to explicitly configure DefaultHandshakeHandler with a list of supported sub-protocols. We will not also check if the WebSocketHandler to use for the WebSocket request is an instance of SubProtocolCapable and obtain the list of sub-protocols that way. The provided SubProtocolWebSocketHandler does implement this interface. Issue: SPR-11111
-
由 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
-
- 24 11月, 2013 1 次提交
-
-
由 Rossen Stoyanchev 提交于
Before this change spring-messaging contained a few WebSocket-related classes including WebSocket sub-protocol support for STOMP as well as @EnableWebSocketMessageBroker and related configuration classes. After this change those classes are located in the spring-websocket module under org.springframework.web.socket.messaging. This means the following classes in application configuration must have their packages updated: org.springframework.web.socket.messaging.config.EnableWebSocketMessageBroker org.springframework.web.socket.messaging.config.StompEndpointRegistry org.springframework.web.socket.messaging.config.WebSocketMessageBrokerConfigurer MessageBrokerConfigurer has been renamed to MessageBrokerRegistry and is also located in the above package.
-
- 23 11月, 2013 5 次提交
-
-
由 Juergen Hoeller 提交于
Issue: SPR-11108
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11105
-
- 22 11月, 2013 12 次提交
-
-
由 Sam Brannen 提交于
The tests introduced in this commit demonstrate the current lacking support for composable stereotypes on interfaces (using @Transactional) as a concrete example. Issue: SPR-11108
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
- Added explicit reference to “get” and “find” lookup types in the class-level Javadoc. - Updated documentation for the underlying algorithms in findAnnotation(Method,Class) and findAnnotation(Class,Class) in line with the status quo. - Reverted recent changes to findAnnotationDeclaringClass() by removing meta-annotation support in order to maintain backwards compatibility with previous releases.
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Phillip Webb 提交于
Fix the reference documentation example for ConversionServiceFactoryBean to use a `<set>` instead of a `<list>`. Issue: SPR-10802
-
由 Phillip Webb 提交于
Replace `hsqldb:hsqldb:1.8.0.10` with `org.hsqldb:hsqldb:2.3.1` and fix breaking tests. Issue: SPR-10947
-
由 Phillip Webb 提交于
* SPR-9164: Add BigDecimal support for SpEl numeric operations
-
由 giovannidalloglio 提交于
Prior to this change, SpEL supported numeric operations for int, float, ect. `new java.math.BigDecimal('0.1') > 0` evaluated to false (BigDecimal is truncated to int) This commit introduces support for BigDecimal operations for all mathematical operators. `new java.math.BigDecimal('0.1') > 0` now evaluates to true (the comparison is made with BigDecimals) Issue: SPR-9164
-
由 Phillip Webb 提交于
* fix-SPR-9194: Change SpEL equality operators to use .equals
-
由 Andy Clement 提交于
Prior to this commit the SpEL operators `==` and `!=` were using the Java `==` comparison operator as part of their equality checking. It is more flexible to use the equals() method on Object. Under this commit the change to .equals() has been made and the equality checking code has been pushed into a common method in the Operator superclass. This commit also makes some tweaks to the other operator classes - the Float case was missing from OpGT. Issue: SPR-9194
-
由 Phillip Webb 提交于
-
- 21 11月, 2013 9 次提交
-
-
由 Sam Brannen 提交于
-
由 Sam Brannen 提交于
-
由 Phillip Webb 提交于
-
由 Phillip Webb 提交于
-
由 Phillip Webb 提交于
-
由 Phillip Webb 提交于
Issue: SPR-11057
-
由 Sam Brannen 提交于
Prior to this commit, the getValue(Annotation, String) method in AnnotationUtils failed to retrieve the value of the desired annotation attribute if the annotation itself was not public -- for example if the annotation was declared as package private. This commit addresses this issue by ensuring that getValue(Annotation, String) uses reflection to make the desired annotation attribute method accessible before attempting to invoke it to retrieve the value. Issue: SPR-11104
-
由 Sam Brannen 提交于
As of Gradle 1.8, ‘testReport true’ is deprecated. Thus in order to generate TestNG reports alongside JUnit reports with Gradle 2.0 and beyond, we are now using: getReports().getHtml().setEnabled(true)
-
由 Phillip Webb 提交于
* SPR-11083: Allow instrumentation to be used with Attach API
-