{{ message }}
This repository was archived by the owner on Feb 4, 2024. It is now read-only.
WIP: PoC of new Spring-JMS binding#145
Closed
SvenBunge wants to merge 1 commit into
Closed
Conversation
Contributor
danielwegener
changed the title
Member
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A PoC of spring JMS implementation. It ships an own version of a
MessageConverterwith some wrapping/delegation ability if the user want use an own implementation.On the receiving site it's not possible to get the end of the invocation without wrapping all of the API (like in #143 ) but when I get the manual of Spring JMS right, the consumers are cached in an own threadpool. So it's possible to clean the threads right before the next job I think.
(Maybe we can create some interoperability tests between JMS and SpringJMS. But there is no implementation of a message and bad practice to mock the whole message if we want to test some interoperability.)