v5.0.0.RELEASE v5.0.0.RC1 v5.0.0.M7 v5.0.0.M6 v5.0.0.M5 v5.0.0.M4 v5.0.0.M3 v5.0.0.M2 v5.0.0.M1 v4.3.13.RELEASE v4.3.12.RELEASE v4.3.11.RELEASE v4.3.10.RELEASE v4.3.9.RELEASE v4.3.8.RELEASE v4.3.7.RELEASE v4.3.6.RELEASE v4.3.5.RELEASE v4.3.4.RELEASE v4.3.3.RELEASE v4.3.2.RELEASE v4.3.1.RELEASE v4.3.0.RELEASE v4.3.0.RC1 v4.3.0.M2 v4.3.0.M1 v4.2.12.RELEASE v4.2.11.RELEASE v4.2.10.RELEASE v4.2.9.RELEASE v4.2.8.RELEASE v4.2.7.RELEASE v4.2.6.RELEASE v4.2.5.RELEASE v4.2.4.RELEASE v4.2.3.RELEASE v4.2.2.RELEASE v4.2.1.RELEASE v4.2.0.RELEASE v4.2.0.RC1 v4.2.0.M2 v4.2.0.M1 v4.1.9.RELEASE v4.1.8.RELEASE v4.1.7a.RELEASE v4.1.7.RELEASE v4.1.6.RELEASE v4.1.5.RELEASE v4.1.4.RELEASE v4.1.3.RELEASE v4.1.2.RELEASE v4.1.1.RELEASE v4.1.0.RELEASE v4.1.0.RC1 v4.1.0.M1 v4.0.9.RELEASE v4.0.8.RELEASE v4.0.7.RELEASE v4.0.6.RELEASE v4.0.5.RELEASE v4.0.4.RELEASE v4.0.3.RELEASE v4.0.2.RELEASE v4.0.1.RELEASE v4.0.0.RELEASE v4.0.0.RC1 v4.0.0.M4 v4.0.0.M3 v4.0.0.M2 v4.0.0.M1 v3.0.8.RELEASE v3.0.7.RELEASE v3.0.6.RELEASE v3.0.5.RELEASE v3.0.4.RELEASE v3.0.3.RELEASE v3.0.2a.BUILD v3.0.2.RELEASE v3.0.1.RELEASE v3.0.0.RELEASE v3.0.0.RC1 v3.0.0.M3 v3.0.0.M2 v3.0.0.M1 v2.2.7.RELEASE v2.2.6.RELEASE v2.2.5.RELEASE v2.2.4.RELEASE v2.2.3.RELEASE v2.2.2.RELEASE v2.2.1b.RELEASE v2.2.0.RELEASE v2.2.0.RC3 v2.2.0.RC2 v2.2.0.RC1 v2.2.0.M4 v2.2.0.M4.SPRINT3 v2.2.0.M4.SPRINT2 v2.2.0.M4.SPRINT1 v2.2.0.M3
Nothing to show
Commits on Jan 19, 2018
Commits on Jan 18, 2018
Jan 18, 2018
JIRA: https://jira.spring.io/browse/INT-4379 - shutdown the container when the gateway is stopped Also, improve test suite - at the end of the tests, hundreds of threads are running, some caused by the above but others because `TaskExecutor`s are not shut down - reduce the number of iterations in the JMS pipeline tests to speed things up - change more tests to extend `ActiveMQMultiContextTests`, to keep a single broker up __cherry-pick to 4.3.x__ (perhaps just the gateway fix)
Commits on Jan 16, 2018
JIRA: https://jira.spring.io/browse/INT-4378 Events (e.g. `TcpConnectionOpenEvent` from intercepted connections contain an 'unknown' connection factory name. Delegate to the underlying connection's factory name.
Commits on Jan 11, 2018
Commits on Jan 5, 2018
Commits on Jan 4, 2018
JIRA: https://jira.spring.io/browse/INT-4371 Add an abstract message source that populates the message with a header containing an abstraction that allows the application to acknowledge/reject/requeue the message. (In amqp, for example, this would map to channel.basicAck(tag), channel.basicReject(tag, false), and channel.basicReject(tag, true). With some brokers (such as kafka), acknowledge and reject might be equivalent since there is no automatic DLQ processing in kafka both would simply commit the offset. Also include a strategy interface for a factory to provide the acknowledgment header. Add MessageSourcePollableChannel Fix typo Polishing - PR Comments - remove marker interface; just use presence of the header for auto-ack - remove the MessageSourcePollableChannel - users can use a MethodInterceptor to enhance the message - other PR comments Save entire response to allow customization of the ack/nack actions. Docs, Copyrights; add MessageSourcePollingTemplate Polishing - PR Comments - support disabling auto-ack, when possible. More Utilities * Simple code style polishing
Commits on Jan 2, 2018
Commits on Dec 28, 2017
Commits on Dec 27, 2017
Commits on Dec 19, 2017
Commits on Nov 15, 2017
JIRA: https://jira.spring.io/browse/INT-4363 The JIRA requests making the `MessageHandlerMethodFactory` a bean. This is not possible without a major rework of the `MessagingMethodInvokerHelper`. The problem is that the `InvokerHandlerMethod` s are created before the factory is initialized. In fact, it only works at all since the IHMs have a hard reference to the factory's argument resolvers so, when they are initialized in `initialize()` each handler sees the resolvers. This really needs to be improved but, since we are so close to GA, the compromise was to add a `HandlerMethodArgumentResolversHolder` which holds the standard resolvers which are then wired into the factory (along with the message converter). Delaying the creation of the `InvokerHandlerMethod` is not trivial; today they are built in the CTOR; moving it to `initialize()` would prevent the fast failure for a badly configured bean; the proper solution might be to make the MMIHs beans themselves. Polishing - PR Comments
Commits on Nov 13, 2017
JIRA: https://jira.spring.io/browse/INT-4362 INT-4312 added a JSON conversion when there is a single method with a non-String parameter. Add more tests for parameters of type `Message`. Catch conversion exceptions and use the message as-is if the conversion fails.
JIRA: https://jira.spring.io/browse/INT-4364 Always let the OS choose the ports for tests. Just one test remains (RMI) because there appears to be no way to obtain the port after creating a registry with a 0 port. This test has been switched to use the Spring utility. Polishing - PR Comments
Commits on Oct 30, 2017
Commits on Sep 26, 2017
Commits on Sep 25, 2017
Commits on Sep 14, 2017
JIRA: https://jira.spring.io/browse/INT-4312 If there is a single eligible method, the message content is JSON and the method parameter doesn't match the payload, perform JSON conversion if there is an ObjectMapper available.
Commits on Sep 11, 2017
Commits on Sep 8, 2017
JIRA: https://jira.spring.io/browse/INT-4255 - Support embedding headers for transports that don't support headers (TCP, Kafka, etc) - Use the new message-aware Jackson ObjectMapper - Provide a mechanism to more efficiently support byte payloads (avoid Base64 encoding) - Support decoding "legacy" SCSt embedded headers Polishing; PR Comments - Add Support to MQTT and TCP Switch to simple patterns instead of regex * Fix JavaDoc typo * Upgrade to Jackson 2.9.1
JIRA: https://jira.spring.io/browse/INT-4342 Use similar code to Spring AMQP to add white list support for Integration's use of the `DeserializingMessageConverter`; introduce the `WhiteListDeserializingMessageConverter`. Polishing Missed this change in PR. Fix XSD attribute
Commits on Sep 1, 2017
JIRA: https://jira.spring.io/browse/INT-4333 If the user has explicitly set management properties in a bean definition, the configurer should not override those settings with defaults.
JIRA: https://jira.spring.io/browse/INT-4336 Don't add "hidden" unreachable methods to the map in the `GatewayProxyFactoryBean`. The methods can never be executed and may not have all expected properties; they should not appear in the graph at all since they are unreachable. Also add defensive coding to the `IntegrationGraphServer` to avoid NPEs when unexpected conditions arise.
Commits on Aug 23, 2017