The default executor for sending messages from the IMAP IDLE
channel adapter is a single threaded thread pool.
If the default executor is used (no executor injected), shut
it down when the adapter is stopped.
INT-2820 Polishing
If using the default sendingTaskExecutor, create a new one
when restarted.
Add test to restart adapter after stop.
INT-2820 Polishing
Review comments; protect for null sendingTaskExecutor.
Previously, if an IMAP server supports IDLE, but not
RECENT, no existing messages were retrieved until a new
message arrived.
INT-2821 Polishing - Fix Race Condition
Use searchForMessages() when server doesn't support RECENT.
Simply skipping the first idle() doesn't work
because receive() closes the folder, there was a race condition
where a new message could arrive between the previous receive()
and folder.open() in waitForMessages().
Updated mock test so that first call to waitForMessages() finds
messages and does not idle(), and subsequent calls does not
find messages and goes to idle().
Also tested in the debugger against gmail which (at the time of
writing) does not support RECENT.
Polishing
Renaming and Repackaging.
INT-2798 Add More Tests
Add more tests for Store Outbound Adapter.
INT-2798 Polishing
More tests - zset increment/overwrite with Map payload.
- use different value for simple overwrite.
Pull transaction synchronization code up from SPCA
to AbstractPollingEndpoint, providing support for
transaction synchronization in PollingConsumer.
Also, ensure headers are copied to any message generated by the
ExpressionEvaluatingTransactionSynchronizationProcessor.
INT-2799 Use StringRedisTemplate by default on both inbound
and outbound store adapters.
Use a RedisTemplate with String key serializers and JDK
value serializers on the outbound store adapter if
'extract-payload-elements' is false.
INT-2811 Remove the ability to configure serializers on the adapters.
Use an external RedisTemplate for customized serialization
strategies.
INT-2811 Polishing (Review)
Polishing and updated Reference Doc.
polishing
using setters instead of ctor args for key or keyExpression
INT-2811 Polishing
Improve message when handler not initialized.
Add test for storing a simple value in a map.
The final remote directory expression processor was being
used instead of the temporary directory expression processor.
Add a test to confirm the correct processors are used.
OSGI version ranges were incorrect for oxm because it moved
to core. This precluded use with Spring 3.1 with OSGI.
Update oxm version range to match other Spring core modules.
Also update maximum for Spring-WS to < 3.0.0 and minumum to 2.0.0.
Also fix bundlor version ranges for new JPA module.
1.1.3.RELEASE includes enhanced JsonMessageConverter to
support applications using the ObjectToJsonTransformer.
avoid warning in AmqpOutboundGatewayParserTests
Add note about content-type for the <object-to-json-transformer/>
and the caveat for when using AMQP adapters.
INT-2797 Polishing
Add alternative solutions, including setting a defaultType on
an inbound JsonMessageConverter.
INT-2805 Update JavaMail to 1.4.5
There is a need to fetch the entire email message before the folder
is closed. Once the folder is closed, you cannot perform any
more operations on the message.
Prior to RC1, the message was copied, which forced an eager fetch.
Add code to copy the message.
Also, transaction synchronization operations need access to a folder
instance to perform operations, such as delete, on a message.
Add a wrapper to lazily create a folder instance in message.getFolder()
when needed.
Add documentation to explain that messages must be re-fetched before
performing transaction synchronization operations.
JavaMail 1.4.5 is now Open Source, which makes debugging much
easier.
Previously, the ability to customize the search term
strategy was added to the IMAP Idle adapter; it should
also be available to the polled IMAP adapter.
Add the attribute.
Remove some obsolete code from the parser.
INT-2794 - Spring Integration WS should depend on spring-webmvc
INT-2795 - Update Spring WS dependency to 2.1.1.RELEASE
INT-2796 - Update Spring-XML dependency to 2.1.1.RELEASE
* INT-2779:
INT-2779 spring-data-mongo upgrade upgraded to spring-data-mongo-1.1.1.RELEASE removed safety logic that was put temporarily to address DATAMONGO-550/551
Previously, the connection resource was hard-coded to 'Smack' by
default.
According to RFC 6120 section 7.6. Server-Generated Resource Identifier
if the connecting client does not provide resource string, server will
generate RANDOM one for it.
Smack API allows this by providing null resource in
XMPPConnection#login(username, password, resource) call.
See Smack's SASLAuthentication documentation.
Tested with XMPP sample (including default resource and configuring
as 'Smack').
