The recent refactoring of the messaging package (converting it from XML-based bean definitions to POJOs) accidentally left out the part where the message consumers are registered on JMS queues. Since leaving this out does not cause any errors during startup and since there are no tests that test the JMS integration, this bug was undetected until now.
What
Adds registration of message consumers to the JMS queues converted from the old bean XML-configuration. Also updates the example SOAP message with values that I used to test this locally instead of it's previous invalid values.
Let me know if you want me to add some automated integration tests to verify this as well.
Why
The recent refactoring of the messaging package (converting it from XML-based bean definitions to POJOs) accidentally left out the part where the message consumers are registered on JMS queues. Since leaving this out does not cause any errors during startup and since there are no tests that test the JMS integration, this bug was undetected until now.
What
Adds registration of message consumers to the JMS queues converted from the old bean XML-configuration. Also updates the example SOAP message with values that I used to test this locally instead of it's previous invalid values.
Let me know if you want me to add some automated integration tests to verify this as well.