You should always use our springsupport.jar. There are issues with Spring, especially with a TransactionManager. For example, if you use the default values on the DefaultMessageListenerContainer, it will use receive(1000) and runs a commit every second. If you don't use pooling, it will create/destroy sessions etc on every go.
I got a strange exception from DefaultMessageListenerContainer stating that a message was received while the listener was stopped. Don't know what that means but I was able to get over it by adding a property. See attached Spring context.
swiftmq-context.xmlThe problem with many producers for temp queues can be solved a) by using an unidentified producer or b) by reducing the poolExpiration. Both are supported by our springsupport. The usual way is a) in request/reply. I don't know how you can use an unidentified producer in Spring's request/reply.
