AMQP-240 Minor Doc Correction
Merge pull request #74 from garyrussell/AMQP-240a

  AMQP-240 Minor Doc Correction
AMQP-275 Physically Close Channel on Listener Stop

When stopping a listener container, physically close the channel
so any queued, but not yet processed messages go back to Ready
instead of remaining un-ack'd.

Rename methods to is/setPhysicalCloseRequired()
Merge pull request #73 from garyrussell/AMQP-275a

* AMQP-275: Physically Close Channel on Listener Stop
AMQP-275 Reduce StopStart Test Size

Reduce number of messages
Reduce concurrency and prefetch
Increase stop/start frequency
AMQP-274 Local Transaction Issues

When running a listener container with local transactions
(channelTransacted, and no external transaction manager), the
consumer's channel is bound to the thread for use by downstream
RabbitTemplates.

However, the syncronizedWithTransaction boolean was not set so
the RabbitTemplate closed the channel after its operation.

We should never close the consumer's channel.

The solution is to set the boolean when binding the resource.

In addition, when using a RabbitTransactionManager, the
RabbitResourceHolder.closeAll() method would close the consumer's
channel.

Previously, the consumer's channel was registered with a
ThreadLocal in the ConnectionFactoryUtils. This enabled
the doGetTransactionalResourceHolder method to bind the
consumer's channel.

The RabbitResourceHolder.closeAll() now examines the channels
is it closing and skips the close for the consumer's channel.

Added tests to the Local and External transaction test cases
to ensure the appropriate channel.close() calls are executed,
depending on the scenario. e.g. a local transaction with
exposeListenerChannel=false should close() the exposed channel
but not the consumer's channel.
Merge pull request #72 from garyrussell/AMQP-274

* AMQP-274: Local Transaction Issues
AMQP-276 Rename spring-amqp-core to spring-amqp

Revert subproject name back to pre-gradle name to avoid
maven artifact name change.

This was done in the 1.1.x during the 1.1.2 build process.
AMQP-277 Add DefaultType to DefaultClassMapper

Permit the use of a JsonMessageConverter when no type information
is provided in the MessageProperties and the type is known.
Merge pull request #75 from garyrussell/AMQP-276+7

* AMQP-276+7:
  AMQP-277 Add DefaultType to DefaultClassMapper
  AMQP-276 Rename spring-amqp-core to spring-amqp
AMQP-280 Fix Test Case Race Condition

stop() container AFTER testing that mock.close() was never called.
AMQP-278 White Space Violations

Remove trailing white spaces from all java, xml and 1.1 xsd files.

    git log -p -b

shows no changes other than white space removal.
AMQP-283/284 Upgrade to RabbitMQ 3.0.0

AMQP-283 Upgrade Rabbit Client to 3.0.0.

AMQP-284 Deprecate immediate (publish) flag, Deprecate
Federated Exchanges.

Exchange Federation is no longer configured using
exchange declaration.

Federation: Pre 3.0
Configuration lives in the configuration file.
You must ensure all nodes in a cluster have the same configuration.
The broker must be restarted for changes to take effect.
Federated exchanges are of a special type, and must be declared as such by AMQP clients.

Federation: 3.0
Configuration is stored in the broker database, manipulated with rabbitmqctl or the management plugin.
All nodes in a cluster automatically have the same configuration.
Changes to federation take effect immediately.
Federated exchanges are transparent to clients; exchanges can become federated at any time.

AMQP-287 Add Configurable Consumer Start Timeout

See https://jira.springsource.org/browse/AMQP-287

Allow the configuration of an increased timeout for when
SYN packets are dropped.

Revert "AMQP-287 Add Configurable Consumer Start Timeout"

This reverts commit d80fb35070cd53eac9e79fff1e395e28a270521a.

AMQP-283 Fix Typos in Schema Docs

PR Review

AMQP-287 Slow Startup is No Longer Fatal

Previously, if the consumer failed to start within 60 seconds
it was considered fatal. If the server is down and the network
is configured to take more than 60 seconds to report dropped
SYN (socket open) packets, the context would fail to initialize.

This is not consistent with, say, when the server is up but the
broker is down. In that case, the connection failure is detected
immediately, and the consumer starts attempting to reconnect - it
is NOT considered a fatal exception.

This change removes the fatal exception thrown when the consumer
fails to start in the 60 seconds (while still waiting for up to
60 seconds to see if a real fatal exception occurred).

Note that a real fatal exception (such as failure to declare the
queue(s) passively) will still cause the context to fail to initialize,
if it occurs within 60 seconds of the consumer starting.
Merge pull request #78 from garyrussell/AMQP-287

* AMQP-283/284/287

Upgrade to RabbitMQ 3.0.0

Deprecate immediate (publish) flag

Deprecate Federated Exchanges

Add Configurable Consumer Start Timeout