Skip to content
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

Error when notification are acknowledged #9661

Closed
exalate-issue-sync bot opened this issue Apr 8, 2024 · 1 comment
Closed

Error when notification are acknowledged #9661

exalate-issue-sync bot opened this issue Apr 8, 2024 · 1 comment

Comments

@exalate-issue-sync
Copy link

exalate-issue-sync bot commented Apr 8, 2024

Since 4.0, when a UI notification is acknowledge the response return a 500 or 400 because JAX-RS/Jackson refuse to serialize an empty bean on a NO_CONTENT status.

com.fasterxml.jackson.databind.exc.InvalidDefinitionException: No serializer found for class java.lang.Object and no properties discovered to create BeanSerializer (to avoid exception, disable SerializationFeature.FAIL_ON_EMPTY_BEANS) (through reference chain: org.glassfish.jersey.message.internal.OutboundJaxrsResponse$Builder["context"]~~>org.glassfish.jersey.message.internal.OutboundMessageContext["runtimeDelegateDecorator"]~~>org.glassfish.jersey.internal.RuntimeDelegateDecorator$ConfigurableRuntimeDelegate["runtimeDelegate"]~~>org.glassfish.jersey.internal.RuntimeDelegateImpl["entityPartBuilderProvider"]~~>org.glassfish.jersey.internal.util.collection.Values$LazyValueImpl["lock"])
Copy link
Author

This issue will be fixed in versions 4.2.9, 4.1.19, 4.0.16, 4.3.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

0 participants