- 27 3月, 2014 7 次提交
-
-
由 Spring Buildmaster 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11606 (cherry picked from commit a4a2e80f)
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Although the need to map the ASYNC dispatcher type to a Filter was already mentioned, it wasn't very prominent and can be quite critical in some cases. This change addresses that. Issue: SPR-10440
-
由 Juergen Hoeller 提交于
Issue: SPR-11609
-
由 Juergen Hoeller 提交于
Issue: SPR-11609
-
由 Juergen Hoeller 提交于
-
- 26 3月, 2014 16 次提交
-
-
由 Rossen Stoyanchev 提交于
This reverts commit 3474afb1. Unfortunately this change is likely to cause issues for applications that use regular expressions in a URI variable. I think we will have to leave at: if there are any dots in the last segment of the request path, regardless of whether they're in a URI var or not, the suffix pattern match is off. Issue: SPR-11532
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11608
-
由 Juergen Hoeller 提交于
Issue: SPR-11606
-
由 Phillip Webb 提交于
This reverts commit 4788875a.
-
由 Spring Buildmaster 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11450
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11592
-
由 Juergen Hoeller 提交于
Issue: SPR-11592
-
由 Arjen Poutsma 提交于
Improved the SAX to StAX (and vice-versa) bridge exposed via StaxUtils. The old integration had some issues with namespace declaration attributes, brought to light in a XMLUnit upgrade. Issue: SPR-11549
-
由 Sam Brannen 提交于
Changes introduced in conjunction with issue SPR-11475 altered the behavior of StandardAnnotationMetadata such that annotations could be detected on superclasses, specifically in the case where the AnnotatedElementUtils.getAllAnnotationAttributes() method is invoked to obtain multiple annotations of the same type (on the lowest level in the class hierarchy), as is the case for @Profile and @Conditional. This commit partially reverts these changes as follows: - All methods in AnnotatedElementUtils now set the traverseClassHierarchy to false, thereby effectively reverting the changes made in commit 1d30bf83. Note, however, that the changes made to AnnotationUtils remain in place. - Introduced tests in AnnotationMetadataTests that verify behavior present in Spring Framework 4.0.2 and earlier. - Updated tests in AnnotatedElementUtilsTests so that they pass against the reverted changes (i.e., align with the behavior present in Spring Framework 4.0.2 and earlier). - Refined Javadoc in AnnotationMetadata with regard to annotations being "present" vs. "defined". - Refined Javadoc in AnnotatedTypeMetadata. Issue: SPR-11475, SPR-11595
-
由 Stephane Nicoll 提交于
* pull424: typo in pointcut expression
-
由 md42 提交于
-
- 25 3月, 2014 17 次提交
-
-
由 Stephane Nicoll 提交于
-
由 Sebastien Deleuze 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11584
-
由 Stephane Nicoll 提交于
This commit validates that the payload type of the message is assignable to the one declared in the method signature. If that is not the case, a meaningful exception message is thrown with the types mismatch. Prior to this commit, only the Message interface could be defined in the method signature: it is now possible to define a sub-class of Message if necessary which will match as long as the Message parameter is assignable to that type. Issue: SPR-11584
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11578
-
由 Rossen Stoyanchev 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-11239
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11575
-
由 Rossen Stoyanchev 提交于
This change updates the XML namespace to match a change already made to the Java config.
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11578
-
由 Juergen Hoeller 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11527
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11527
-
由 Rossen Stoyanchev 提交于
Issue: SPR-11527
-
由 Sebastien Deleuze 提交于
BufferingStompDecoder message buffer size limit can now be configured with JavaConfig MessageBrokerRegistry.setMessageBufferSizeLimit() or with XML <websocket:message-brocker message-buffer-size="">. Issue: SPR-11527
-
由 Rossen Stoyanchev 提交于
Before this change the StompDecoder decoded and returned only the first Message in the ByteBuffer passed to it. So to obtain all messages from the buffer, one had to loop passing the same buffer in until no more complete STOMP frames could be decoded. This chage modifies StompDecoder to return List<Message> after exhaustively decoding all available STOMP frames from the input buffer. Also an overloaded decode method allows passing in Map that will be populated with any headers successfully parsed, which is useful for "peeking" at the "content-length" header. This change also adds a BufferingStompDecoder sub-class which buffers any content left in the input buffer after parsing one or more STOMP frames. This sub-class can also deal with fragmented messages, re-assembling them and parsing as a whole message. Issue: SPR-11527
-