forked from zmalltalker/stomp
-
Notifications
You must be signed in to change notification settings - Fork 80
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support Artemis JMS/JNDI Destination Names in Unit Tests #128
Comments
@mikola-spb Since you run Artemis, ..... are you interested in working on this? Let me know please. Regards, Guy |
Needs to support topics as well. |
Hi, sorry missed you comment. I won't promise but will try to have a look. Support of Artemis in tests is a good thing for sure |
Artemis support in unit tests was completed in stages. For the record, I use the following for unit tests:
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Background: Artemis by default uses a JMS/JNDI style of destination names.
Each destination name is prefixed by 'jms.queue.', and the separator character for destinations is a period ('.').
Example destination names:
Changes:
Add support of a STOMP_ARTEMIS environment variable to detect if Artemis is the broker used.
Modify test/test_helper.rb method make_destination to detect the STOMP_ARTEMIS environment variable, and return a proper destination name.
Modify other unit tests as required to support Artemis destination names, and any observed broker specific behavior.
With this modification, unit tests that resemble the following should run:
The text was updated successfully, but these errors were encountered: