-
Notifications
You must be signed in to change notification settings - Fork 84
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
AMQP Rabbit #235
Comments
I've never used Rabbit - it would really help if you'd say what happens with the code that you've already tried. Does it throw an exception? What happens? |
It throws an exception Not sure if I an sending it correctly across to rabbit.
|
As I said, I've never used Rabbit, so I don't know on that front. Are you able to decode the result of calling Fundamentally you're encoding this using binary content mode, so I wouldn't expect it to try to deserialize using structured content mode, unless you're setting a content type somewhere that makes it look like it's structured. |
Yeah I am able to encode and decode on the publisher side.
Tried using both binary and structured modes.
Will give a another try tomorrow.
…On Wed, 17 Aug 2022, 18:39 Jon Skeet, ***@***.***> wrote:
Not sure if I an sending it correctly across to rabbit.
As I said, I've never used Rabbit, so I don't know on that front.
Are you able to decode the result of calling Encode, i.e. getting
everything to work from a CloudEvent to an encoded message and back again
*without* actually sending it to Rabbit?
Fundamentally you're encoding this using binary content mode, so I
wouldn't expect it to try to deserialize using structured content mode,
unless you're setting a content type somewhere that makes it *look* like
it's structured.
—
Reply to this email directly, view it on GitHub
<#235 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBEX5SQJKOS47IDEFE523DVZUITFANCNFSM56Z76SAQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
In that case it's presumably something to do with how you're sending and receiving the message - which I won't be able to help with, I'm afraid (and which we can't even see completely in terms of the code you've provided). I notice that you're only using the body of |
Ok cool.
Usually with rabbit if I send a serialized model to rabbit. The consumer is
able to deserialize the body of the basicDeliverEventArgs into the
published model type.
Its only now that I'm trying to use the cloud event model that is converted
to an AMQP encoded message that I'm having trouble with converting back
into a cloud event message on the consumer side.
Il try play around alittle more and il post find findings.
…On Wed, 17 Aug 2022, 18:50 Jon Skeet, ***@***.***> wrote:
Yeah I am able to encode and decode on the publisher side.
In that case it's presumably something to do with how you're sending and
receiving the message - which I won't be able to help with, I'm afraid (and
which we can't even see completely in terms of the code you've provided).
I notice that you're only using the *body* of BasicDeliverEventArgs - I
don't know whether that's the problem, but it's worth looking into.
Fundamentally if the receiving side doesn't get back the same data that the
publisher side sent, that's going to be a problem - you might want to ask
in a Rabbit-specific repo/forum.
—
Reply to this email directly, view it on GitHub
<#235 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABBEX5WNESPWUOXJO4DF3YTVZUJ5LANCNFSM56Z76SAQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Hi,
Can you please provide an example/documentation how to dispatch and consume a message to and from rabbitMQ using ToAmqpMessage() ?
Consumer
The text was updated successfully, but these errors were encountered: