Spring Framework Reference Documentation 4.3.26.RELEASEintroduction, see the Chapter 26, WebSocket Support section. Testing Improvements In addition to pruning of deprecated code within the spring-test module, Spring Framework 4.0 introduces several new features objects through the HTTP protocol, unless you’re tunneling the RMI traffic. RMI is a fairly heavy-weight protocol in that it supports full-object serialization which is important when using a complex data0 码力 | 1323 页 | 4.08 MB | 1 年前3- Spring Framework Reference Documentation v4.3.2introduction, see the Chapter 26, WebSocket Support section. Testing Improvements In addition to pruning of deprecated code within the spring-test module, Spring Framework 4.0 introduces several new features objects through the HTTP protocol, unless you’re tunneling the RMI traffic. RMI is a fairly heavy-weight protocol in that it supports full-object serialization which is important when using a complex data0 码力 | 1311 页 | 4.07 MB | 1 年前3
Spring Framework Reference Documentation 4.3.26.RELEASEintroduction, see the Chapter 26, WebSocket Support section. 3.9 Testing Improvements In addition to pruning of deprecated code within the spring-test module, Spring Framework 4.0 introduces several new features objects through the HTTP protocol, unless you’re tunneling the RMI traffic. RMI is a fairly heavy-weight protocol in that it supports full-object serialization which is important when using a complex data0 码力 | 916 页 | 5.52 MB | 1 年前3- Spring Framework Reference Documentation v4.3.2introduction, see the Chapter 26, WebSocket Support section. 3.9 Testing Improvements In addition to pruning of deprecated code within the spring-test module, Spring Framework 4.0 introduces several new features objects through the HTTP protocol, unless you’re tunneling the RMI traffic. RMI is a fairly heavy-weight protocol in that it supports full-object serialization which is important when using a complex data0 码力 | 907 页 | 5.46 MB | 1 年前3
Spring Framework 2.5.1 Changelognot insisting on a QueueConnectionFactory anymore * MethodListenerAdapter uses type difference weight algorithm to choose between ambiguous listener methods * DefaultMessageListenerContainer catches util * AutoPopulatingList is serializable now * MethodInvoker (and subclasses) use type difference weight algorithm to choose between multiple matching methods * FreeMarker "formSingleSelect" macro also0 码力 | 84 页 | 239.53 KB | 1 年前3- Spring Framework 2.5.2 Changelognot insisting on a QueueConnectionFactory anymore * MethodListenerAdapter uses type difference weight algorithm to choose between ambiguous listener methods * DefaultMessageListenerContainer catches util * AutoPopulatingList is serializable now * MethodInvoker (and subclasses) use type difference weight algorithm to choose between multiple matching methods * FreeMarker "formSingleSelect" macro also0 码力 | 91 页 | 260.30 KB | 1 年前3
- Spring Framework 2.5.3 Changelognot insisting on a QueueConnectionFactory anymore * MethodListenerAdapter uses type difference weight algorithm to choose between ambiguous listener methods * DefaultMessageListenerContainer catches util * AutoPopulatingList is serializable now * MethodInvoker (and subclasses) use type difference weight algorithm to choose between multiple matching methods * FreeMarker "formSingleSelect" macro also0 码力 | 95 页 | 274.89 KB | 1 年前3
- Spring Framework 2.5.4 Changelognot insisting on a QueueConnectionFactory anymore * MethodListenerAdapter uses type difference weight algorithm to choose between ambiguous listener methods * DefaultMessageListenerContainer catches util * AutoPopulatingList is serializable now * MethodInvoker (and subclasses) use type difference weight algorithm to choose between multiple matching methods * FreeMarker "formSingleSelect" macro also0 码力 | 97 页 | 278.81 KB | 1 年前3
- Spring Framework 2.5.5 Changelognot insisting on a QueueConnectionFactory anymore * MethodListenerAdapter uses type difference weight algorithm to choose between ambiguous listener methods * DefaultMessageListenerContainer catches util * AutoPopulatingList is serializable now * MethodInvoker (and subclasses) use type difference weight algorithm to choose between multiple matching methods * FreeMarker "formSingleSelect" macro also0 码力 | 101 页 | 291.00 KB | 1 年前3
- Spring Framework 2.5.6 Changelognot insisting on a QueueConnectionFactory anymore * MethodListenerAdapter uses type difference weight algorithm to choose between ambiguous listener methods * DefaultMessageListenerContainer catches util * AutoPopulatingList is serializable now * MethodInvoker (and subclasses) use type difference weight algorithm to choose between multiple matching methods * FreeMarker "formSingleSelect" macro also0 码力 | 106 页 | 302.13 KB | 1 年前3
共 112 条
- 1
- 2
- 3
- 4
- 5
- 6
- 12