- 27 10月, 2014 8 次提交
-
-
由 Rossen Stoyanchev 提交于
-
由 Sebastien Deleuze 提交于
Issue: SPR-12379
-
由 Juergen Hoeller 提交于
Issue: SPR-10994
-
由 Juergen Hoeller 提交于
Issue: SPR-10767
-
由 Stephane Nicoll 提交于
* SPR-12378: Remove unnecessary null check
-
由 Seo, Kyung-Seok 提交于
Issue: SPR-12378
-
由 Sebastien Deleuze 提交于
Issues: SPR-12283
-
由 Sebastien Deleuze 提交于
This commit introduces a new OriginHandshakeInterceptor. It filters Origin header value against a list of allowed origins. AbstractSockJsService as been modified to: - Reject CORS requests with forbidden origins - Disable transport types that does not support CORS when an origin check is required - Use the Origin request header value instead of "*" for Access-Control-Allow-Origin response header value (mandatory when Access-Control-Allow-Credentials=true) - Return CORS header only if the request contains an Origin header It is possible to configure easily this behavior thanks to JavaConfig API WebSocketHandlerRegistration#addAllowedOrigins(String...) and StompWebSocketEndpointRegistration#addAllowedOrigins(String...). It is also possible to configure it using the websocket XML namespace. Please notice that this commit does not change the default behavior: cross origin requests are still enabled by default. Issues: SPR-12226
-
- 26 10月, 2014 1 次提交
-
-
由 Andy Clement 提交于
-
- 25 10月, 2014 1 次提交
-
-
由 Andy Clement 提交于
These changes provide more robust handling of function reference compilation in SpEL expressions. Prior to this change the isCompilable check was not performing enough visibility checks on the proposed target function, causing bytecode to be generated that would lead to an IllegalAccessError. The changes also bring the argument handling for function invocation completely inline with that used for method invocation allowing some code to be deleted. Many new tests are also included for function reference compilation. Issue: SPR-12359
-
- 24 10月, 2014 10 次提交
-
-
由 Rossen Stoyanchev 提交于
Before this change the simple broker simply removed subscriptions upon receiving a DISCONNECT message assuming it was a result of a client STOMP WebSocket session ending. However, if the server-side application sends a DISCONNECT to the broker in order to terminate a session, the STOMP WebSocket session could remain unware without any further action. This change ensures the simple broker sends a DISCONNECT_ACK message downstream whenever it receives a DISCONNECT. Issue: SPR-12288
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
With SPR-9293, it is now possible to HTML escape text while taking into account the current response encoding. When using UTF-* encodings, only XML markup significant characters are escaped, since UTF-* natively support those characters. This commit adds a new servlet context parameter to enable this fix by default in a Spring MVC application: <context-param> <param-name>responseEncodedHtmlEscape</param-name> <param-value>true</param-value> </context-param> Issue: SPR-12350, SPR-12132
-
由 Stephane Nicoll 提交于
* SPR-12363: Performance improvement
-
由 Sang Gi Ryu 提交于
Use entrySet instead of keySet followed by a lookup per key as the former is more efficient. Issue: SPR-12363
-
由 Stephane Nicoll 提交于
This commits complements 222d2b16 for another required dependency. javax.persistence.Entity was previously required, regardless of which aspects were actually used by the project. It is now optional and will not break the build if it is not present. Note that the side effect is that AnnotationDrivenStaticEntityMockingControl is disabled as well if the JPA API is not available. Issue: SPR-6819
-
由 Stephane Nicoll 提交于
Prior to this commit, a project using compile time weaving upgrading to 4.1 was forced to add spring-context-support and the jcache API in order to build. This problem is not new really: spring-aspects holds all aspects provided by the framework and they all are evaluated when compiling. 4.1 just happens to define a new aspect that requires extra dependencies. This commit uses a new annotation of AspectJ 1.8.3. When @RequiredTypes is added on an aspect, it is evaluated only if the classes defined on the annotation are actually present. If they are not, the aspect is disabled and does not break the build. Issue: SPR-12163
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12370
-
由 Rossen Stoyanchev 提交于
This change adds a ChannelInterceptor that flips the immutable flag on messages being sent. This allows components sending messages to leave the message mutable for interceptors to further apply modifications before the message is sent (and exposed to concurrency). The interceptor is automatically added with the STOMP/WebSocket Java and XML config and the StompSubProtocolHandler leaves parsed incoming messages mutable so they can be further modified before being sent. Issue: SPR-12321
-
由 Craig Andrews 提交于
Issue: SPR-9293
-
- 23 10月, 2014 9 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Also includes order preservation for resource results with Tiles 2 as well as retrieval failure logging with Tiles 3. Issue: SPR-12362
-
由 Sebastien Deleuze 提交于
Issue: SPR-12366
-
由 Juergen Hoeller 提交于
Issue: SPR-12349
-
由 Juergen Hoeller 提交于
Issue: SPR-12365
-
由 Rossen Stoyanchev 提交于
-
由 Rossen Stoyanchev 提交于
Issue: SPR-12347
-
由 Sam Brannen 提交于
-
由 Brian Clozel 提交于
Issue: SPR-12286
-
- 22 10月, 2014 10 次提交
-
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12191
-
由 Brian Clozel 提交于
During the HTTP Content Negotiation phase, the ContentNegotiationManager uses configured ContentNegotiationStrategy(ies) to define the list of content types accepted by the client. When HTTP clients don't send Accept headers, nor use a configured file extension in the request, nor a request param, developers can define a default content type using the ContentNegotiationConfigurer.defaultContentType() method. This change adds a new overloaded defaultContentType method that takes a ContentNegotiationStrategy as an argument. This strategy will take the current request as an argument and return a default content type. Issue: SPR-12286
-
由 Juergen Hoeller 提交于
Issue: SPR-12334 (cherry picked from commit 6e5711a7)
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
Issue: SPR-12334
-
由 Juergen Hoeller 提交于
Latest dependency updates (EhCache 2.9, Joda-Time 2.5, Jackson 2.4.3, Tiles 3.0.5, Tomcat 8.0.14, FreeMarker 2.3.21)
-
由 Juergen Hoeller 提交于
Consistent throwing of BeanInstantiationException for factory methods, including a hint about circular references Issue: SPR-12317
-
由 Juergen Hoeller 提交于
-
由 Juergen Hoeller 提交于
EclipseLinkJpaDialect's getJdbcConnection uses a lazy ConnectionHandle (allowing for deferred internal transaction begin) Issue: SPR-7753
-
- 21 10月, 2014 1 次提交
-
-
由 Andy Clement 提交于
Building on the initial work for SPR-12326, this commit addresses three problems: Firstly the ReflectiveMethodResolver is modified to consider a direct parameter match more important than a varargs match. Also in that same type when there are a number of close matches, the first one is taken rather than the last one. Secondly more testcases and better support have been added for the case of passing a single parameter to a varargs accepting method. Finally it is possible to set the root context object indirectly and not pass it on getValue() calls to the expression objects but not all variants of getValue() were handling that. This is now fixed. Issue: SPR-12326
-