5944e34b6e
Initial Commit Add support for multiple acks in one call. AMQP-213 Polishing Move confirmation state to PublisherCallbackChannel. Allows the RabbitTemplate to handle confirms from multiple channels. Remove unnecessary synchronization. Add tests for multiple threads - verifying the functionality when more than one thread concurrently uses the template. NOTES: The CF cache size must be large enough to cover the number of required channels - otherwise the channel is closed before the confirms are received. This could be alleviated by not closing channels if P.C. are turned on. Each PublisherCallbackConnection has two maps, the first map (seqToListener) identifies which listener gets the confirmation. The second map (pendingConfirms) is a map of maps where the key is the listener and the value is a map of pending confirms for that listener. This map is given back to the listener when registering. In this way, the Rabbit template does not need to hold a reference to every connection he has used. Instead, when a connection is closed, the listener is informed via a call to removePendingConfirmsReference(). The listener uses the pending confirms maps to determine if any confirms have expired. Add test for two templates sharing the same factory, ensuring the appropriate template gets the confirmation. AMQP-213 Polishing AMQP-213 Add Support for Basic.Return The rabbit template will be registered to receive return messages if it is provided with a ReturnCallback. Either mandatory or immediate must also be set for returns. mandator and immediate are ignored if no callback is provided. AMQP-213 Polishing The RabbitTemplate can only support one each of ConfirmCallback and ReturnCallback because there is no way to correlate back to the caller. In situations where more than one client is needed, each needs its own RabbitTemplate. The connection factory, and hence the connection and channels, can be shared across templates. AMQP-213 Add Namespace Support for Returns Attributes added to template for mandatory, immediate, return-callback. Also confirm-callback for confirms. AMQP-213 Return Reply Code Etc Pass the reply code, reply text, exchange, and routing key back to the client on returns. AMQP-213 Polishing Fix non-default exchange on convertAndSend. AMQP-213 Polishing PR Review
This project provides support for using Spring and Java with AMQP, and in particular RabbitMQ.
Getting Started
Clone from GIT and then use Maven (2.2.*):
$ git clone ...
$ mvn install -P bootstrap
Use the bootstrap profile only the first time - it enables some
repositories that can't be exposed in the poms by default.
SpringSource ToolSuite users (or Eclipse users with the latest
m2eclipse plugin) can import the projects as existing Eclipse
projects. There are plenty of interesting integration tests (names
ending with IntegrationTests) to show the features of the
framework. Sample applications can be found in the Spring AMQP
Samples project.
Spring AMQP is released under the terms of the Apache Software License Version 2.0 (see license.txt).
Distribution Contents
The binary JARs are available in the 'dist' directory, and the source JARs are in the 'src' directory. The reference manual and javadoc are located in the 'docs' directory.
Changelog
Lists of issues addressed per release can be found in JIRA.
Additional Resources
- Spring AMQP Homepage: [http://www.springsource.org/spring-amqp]
- Spring AMQP Source: [http://github.com/SpringSource/spring-amqp]
- Spring AMQP Samples: [http://github.com/SpringSource/spring-amqp-samples]
- Spring AMQP Forum: [http://forum.springsource.org/forumdisplay.php?f=74]
Contributing to Spring AMQP
Here are some ways for you to get involved in the community:
- Get involved with the Spring community on the Spring Community Forums. Please help out on the forum by responding to questions and joining the debate.
- Create JIRA tickets for bugs and new features and comment and vote on the ones that you are interested in.
- Github is for social coding: if you want to write code, we encourage contributions through pull requests from forks of this repository. If you want to contribute code this way, please reference a JIRA ticket as well covering the specific issue you are addressing.
- Watch for upcoming articles on Spring by subscribing to springframework.org
Before we accept a non-trivial patch or pull request we will need you to sign the contributor's agreement. Signing the contributor's agreement does not grant anyone commit rights to the main repository, but it does mean that we can accept your contributions, and you will get an author credit if we do. Active contributors might be asked to join the core team, and given the ability to merge pull requests.
Code Conventions and Housekeeping
None of these is essential for a pull request, but they will all help. They can also be added after the original pull request but before a merge.
- Use the Spring Framework code format conventions (import
eclipse-code-formatter.xmlfrom the root of the project if you are using Eclipse). - Make sure all new .java files to have a simple Javadoc class comment with at least an @author tag identifying you, and preferably at least a paragraph on what the class is for.
- Add the ASF license header comment to all new .java files (copy from existing files in the project)
- Add yourself as an @author to the .java files that you modify substantially (more than cosmetic changes).
- Add some Javadocs and, if you change the namespace, some XSD doc elements.
- A few unit tests would help a lot as well - someone has to do it.
- If no-one else is using your branch, please rebase it against the current master (or other target branch in the main project).