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
Better JMS format #178
Better JMS format #178
Conversation
node.addMixin(FEDORA_OBJECT); | ||
session.save(); | ||
|
||
waitForEntry(1); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe it would be better to just do the loop/waiting for the test below instead of counting messages? It seems like that should be more robust than counting messages.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The question is, when are you done? If you don't stop waiting because you know you have enough messages, you must wait for a timeout.
The alternative would be to do a loop and check each message as it comes in to see if it fulfills the test... would you find that better? I can do that, and that would eliminate the counting (which I completely agree is brittle at best).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, I think looping and checking to see if the test is fulfilled would be better -- more direct and fewer ways to break.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, new commit on the way.
Better JMS format Fixes https://www.pivotaltracker.com/story/show/45629439
Introduces a new, more lightweight alternative message format.