-
Notifications
You must be signed in to change notification settings - Fork 143
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
Migrate Message Sequence #164
Comments
pardahlman
added a commit
that referenced
this issue
Dec 4, 2016
pardahlman
added a commit
that referenced
this issue
Dec 11, 2016
pardahlman
added a commit
that referenced
this issue
Dec 11, 2016
pardahlman
added a commit
that referenced
this issue
Dec 12, 2016
pardahlman
added a commit
that referenced
this issue
Feb 18, 2017
pardahlman
added a commit
that referenced
this issue
Feb 18, 2017
It is not enough that to use MessageRecived, it needs to be Deserialized as well
pardahlman
added a commit
that referenced
this issue
Feb 18, 2017
pardahlman
added a commit
that referenced
this issue
Feb 19, 2017
pardahlman
added a commit
that referenced
this issue
Feb 19, 2017
pardahlman
added a commit
that referenced
this issue
Feb 19, 2017
This is done beause the recieiving part should be responsible for deciding type. If all messages comes in on the same queue, we need to use the type prop from the header, which creates a dependency to type specified in producer.
pardahlman
added a commit
that referenced
this issue
Feb 25, 2017
pardahlman
added a commit
that referenced
this issue
Feb 25, 2017
pardahlman
added a commit
that referenced
this issue
Mar 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 2.0, Message Sequence is a State Machine. The signature will slightly change, as the
IBusClient
no longer is hard coupled to a Message Context.The text was updated successfully, but these errors were encountered: