We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug
When creating a OutboundSseEvent object and returning it back in a REST Endpoint it is not correctly serialized.
OutboundSseEvent
Expected behavior
Server-Side Event is sent back and it is able to be deserialized correctly.
Server-Side Event
Actual behavior
Either an exception that the object cannot be serialized or in case of using
@Produces(MediaType.SERVER_SENT_EVENTS) @SseElementType(MediaType.SERVER_SENT_EVENTS)
Then all properties like name, data, comment ... are serialized as a data and not in the correct fields.
name
data
comment
To Reproduce Steps to reproduce the behavior:
Repo is here: https://github.com/lordofthejars/quarkus-quartz-streams
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered:
OutboundSseEvent is not correctly serialized
b5ac295
Closes quarkusio#10673 (cherry picked from commit dc5f031)
4a46c5c
Successfully merging a pull request may close this issue.
Describe the bug
When creating a
OutboundSseEvent
object and returning it back in a REST Endpoint it is not correctly serialized.Expected behavior
Server-Side Event
is sent back and it is able to be deserialized correctly.Actual behavior
Either an exception that the object cannot be serialized or in case of using
Then all properties like
name
,data
,comment
... are serialized as a data and not in the correct fields.To Reproduce
Steps to reproduce the behavior:
Repo is here: https://github.com/lordofthejars/quarkus-quartz-streams
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: