JIRA: https://jira.spring.io/browse/INTEXT-110
Perform the necessary API Changes (Partioner interface in Kafka is now non-genericized for Keys - concrete Object is the new type for Key)
Unit test updates for an internal Kafka class (MessageMetadata)
Updates for the samples Kafka project to use the new M2 snapshot, Spring 4.0 Messaging changes, other build related minor changes, etc.
* Upgrade to SI 4.0.3 and Boot 1.1.4
* Add `HeaderEnricherSpec#headerChannelsToString()`
* Fix `DslRecipientListRouter` according core changes
* Fix `Amqp` and `Jms` modules for the bug around "All Message creators need a BeanFactory"
using fake `new DefaultListableBeanFactory()` for `(Amqp)JmsChannelFactoryBean`
Configure the Spring IO plugin such that it's only applied when the
build is run with -PplatformVersion=<version>. This platformVersion
property is used to determine the version of the Platform that will
be used when running the springIoCheck task. The plugin can be used
by running a build as follows:
./gradlew clean springIoCheck -PplatformVersion=1.1.0.BUILD-SNAPSHOT -PJDK7_HOME=… -PJDK8_HOME=…
This will test the project on JDK7 and JDK 8 using the dependencies
defined in the latest snapshot of Spring IO Platform 1.1.0.
JIRA: https://jira.spring.io/browse/INTEXT-106
* Upgrade to SI 4.0 and other libs
* Upgrade to Gradle 1.12
* Polisihng for `build.gradle`
* Fix compile warnings
JIRA: https://jira.spring.io/browse/INTEXT-105
Previously the `SplunkIndexWriter` has property `indexName`,
however the XSD for `<int-splunk:index-writer/>` provides the `index` attribute
Rename the property and add parser test
* Add `Spec` implementations for `JmsChannel`s
* Fix the bug around `SourcePollingChannelAdapterFactoryBean` named bean registration
* Remove unused classes
* Add test for `Jms.pollableChannel`
upgrade versions
Conflicts:
spring-integration-splunk/gradle.properties
upgrade gradle version
revert spring integration upgrade version
Add a feature to be able to declare more than one splunk server.
It's a simple failover mechanism with any pooling.
Before give back the Service instance, the framework just try a getInfo call.
To preserve backward compat this check it's not activated per default but only
if the splunk server instance is marked with testOnBorrow.
Sample:
````xml
<int-splunk:server id="splunkServer" host="${splunk.server.host}" port="${splunk.server.port}"
username="${splunk.server.username}" password="${splunk.server.password}"
owner="${splunk.server.owner}" scheme="${splunk.server.scheme}" testOnBorrow="true" />
<int-splunk:server id="splunkServerBackup" host="localhost" port="9999"
username="${splunk.server.username}" password="${splunk.server.password}"
owner="${splunk.server.owner}" scheme="${splunk.server.scheme}" testOnBorrow="true" />
<util:list id="splunkServersList">
<ref bean="splunkServer" />
<ref bean="splunkServerBackup" />
</util:list>
<bean id="splunkServiceFactory" class="org.springframework.integration.splunk.support.SplunkServiceFactory">
<constructor-arg ref="splunkServersList"/>
</bean>
<int-splunk:inbound-channel-adapter id="splunk-notify-order-status-change-channel"
auto-startup="true"
search=""
splunk-server-ref="splunkServer;splunkServerBackup"
channel="notify-order-status-change-input"
mode="BLOCKING"
init-earliest-time="${splunk.order-status-change.init-earliest-time}"
>
<int:poller fixed-rate="${splunk.order-status-change.pooling.rate.time}" time-unit="SECONDS"/>
</int-splunk:inbound-channel-adapter>
````
some changes due to pr comments
Conflicts:
spring-integration-splunk/gradle.properties
formatting: tabs instead of spaces.....
fix documentation with failover mechanism
formatting
formatting
upgrade versions
some changes due to pr comments
fix javadoc issues
1.1 xsd file
Polishing and upgrading
* Move DSL parser logic from `BFPP` to `BPP` as soon as the DSL doesn't populate any `BeanDefinition` - just real objects,
which can be registered with `this.beanFactory.registerSingleton(beanName, component);`
* Add more DSL for `Amqp` 'Namespace' factory and provide tests on the matter
* Comment out `spring-integration-jdbc` and `spring-integration-jpa` dependecies because the provide `spring-jdbc` dependency,
but it causes an issue in Boot: https://github.com/spring-projects/spring-boot/issues/1041
