Quarkus 1.3.x: AMQP Emitter<JsonObject> does not set content-type

[andreas-eberle]

Describe the bug
When using an Emitter<JsonObject> of the quarkus-smallrye-reactive-messaging-amqp extension, Quarkus 1.2.1.Final added the Content-Type: application/json to the properties of the message. This is also documented under https://smallrye.io/smallrye-reactive-messaging/#_forwarding_messages_to_amqp: (Vert.x) JSON Array or JSON Object (send as binary with content type set to application/json)

In Quarkus 1.3.x, the content type property is not set in the message.

Expected behavior
Content type should be set.

Actual behavior
Content type is missing.

To Reproduce
Steps to reproduce the behavior:

1. Download reproducer-smallrye-amqp-emitter-not-working.zip and unzip it.
2. In the unzipped directory run docker-compose up -d to start an activemq broker.
3. Run ./mvnw quarkusDev to start the container
4. Open http://localhost:8080/hello in a browser

[andreas-eberle]

@cescoffier: Is there an option to set the application/json header or might this be a bug in smallrye-reactive-messaging?

[cescoffier]

That will be fixed in Quarkus 1.4 :-)

[cescoffier]

For now, you can send an AMQP MEssage or a Message with OutgoingAmqpMetadata setting the content-type explicitly.

[andreas-eberle]

Thanks! Is it in the CR1 already? Or not yet?

[cescoffier]

Not yet.

[andreas-eberle]

@cescoffier: It seems this didn't make it into 1.4.1.Final, am I right? I still see the same problem.

[cescoffier]

I need to check, but I don't believe this was backported.

[gsmet]

@cescoffier what's the PR?

[cescoffier]

it's more when the reactive messaging 2.0 was integrated.

[gsmet]

Yeah, this wasn't included in 1.4.

[gsmet]

Hmmm, let me correct that. It was included. So there's something else going on.

[cescoffier]

Yes... most probably be a bug.