OK. Figured it out. With Spring 2.x, the DefaultMessageListenerContainer
that we create seems to be automatically started. We don't ever call start
on it. With Spring 3, we need to call start().If I add that call after
the initialize, all the JMS tests pass.
Dan
On Thu December
I added a profile to the build to build/run with the recently released Spring
3. I have it completely building now (although a bunch of warnings as
Spring deprecated a bunch of stuff that we need to call for Spring 2.5),
however, the JMS tests are hanging.
I would really appreciate it i
