1. MethodInvokingHeaderValueMessageProcessor => MessageProcessingHeaderValueMessageProcessor because now he uses MessageProcessor
2. polishing HeaderEnricherParserSupport
3. GroovyHeaderEnricherTests: add check to HeaderValueMessageProcessor for Groovy scripts.
4. build.gradle: add dependency to 'spring-integration-test' for 'spring-integration-groovy'.
ServiceActivatorFactoryBean#createMessageProcessingHandler: force 'processMessage' method-name parameter into constructor ServiceActivatingHandler for MessageProcessor
Test for check 'handlerMethods' in ServiceActivatingHandler's MethodInvokingMessageProcessor
Integration test for <service-activator> with invalid Groovy inline script
Some generated bean names (e.g. LoggingHandler) cause
warnings in STS:
(Warning "Referenced bean
'org.springframework.integration.handler.LoggingHandler#0' not found")
Fix is to register these beans as components so an event is fired.
JMS backed channels can have container-type and
container-class. Parser rejected container-class because
the schema has a default for container-type.
Both attributes are allowed; user must set container-type
appropriately (based on the superclass of the custom class)
when container-class is provided.
JMX Tests failed due to InstanceAlreadyExistsException; name
collisions between MBeans registered in multiple tests.
Adds a domain to the new tests added to fix INT-2413 to
force unique MBean names.
When an AbstractMappingMessageRouter is included in an
ApplicationContext that also has an <int-jmx:mbean-exporter/>,
the @ManagedOperations (set and remove mapping) are no longer
visible to the <control-bus/>.
Adds these methods to a new interface MappingMessageRouterManagement,
thus making them available on the proxy that the MBean exporter
creates.
https://jira.springsource.org/browse/INT-2411
Namespace problem only; the default-output-channel was
not bound to the RecipientListRouter.
Workaround is to declare the router using <bean/> syntax.
STS needs Spring Project Nature to get classpath XSD/Namespace resolution.
When switching back and forth between 2.0 and 2.1, ./gradlew eclipse
removes Spring Project Nature.
It is now added by ./gradlew eclipse when generating eclipse metadata
files.
The AbstractChannelAdapterParser creates an implicit DirectChannel
if the adapter has no 'channel' attribute.
The Event, TCP, and UDP channel adapter parsers did not bind
this channel to the adapter and AC initialization failed with
'outputChannel is required'.
Further, the event schema marked the channel as being 'required',
precluding this feature.
INT-2407 Remove Channel use="required"
Parsers automatically generate the channel when none is provided.
- JMX
- JDBC
- SFTP
- Redis
- Feed
- XMPP
- Mail
- FTP
- HTTP
INT-2393 - Changes in Build.gradle based on Code Review
* Changed line to *jvmArgs "-javaagent:${configurations.jacoco.asPath}=destfile=${buildDir}/jacoco.exec,includes=org.springframework.integration.*"*
* Added *props["sonar.jacoco.reportPath"] = "${buildDirName}/jacoco.exec" to make build work with default build directory*
* Therefore able to remove: *buildDir = "target"*
* Moved *sonar* block to bottom of build script
* Added comments around the **configurations** block
* Switched to use Gradle Properties instead of System Properties for Sonar parameters
INT-2393 - rootProject.hasProperty works
* More simplifications after finding out that **rootProject.hasProperty** works inside the Sonar closure
INT-2393 Based on code review: Fixed build.gradle
Based on Code Review, converted println statement to logger.info in build.gradle
- Touch up title text
- Add 'header' (shows up in upper right and left of frameset)
- Ensure @author attribution shows up (not true by default!)
- Remove now-obsolete custom Javadoc CSS and background image
Picks up changes that solve intermittent tests described at
http://issues.gradle.org/browse/GRADLE-2035
Also uses new snapshot versions of bundlor and docbook plugins that fix
incompatibility problems with 1.0-milestone-8.
* MessageChannel was moved from core to the base package.
* ChannelResolver moved from core to support.
* TcpConnectionInterceptorFactoryChain was incorrect.
