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

smallrye-reactive-messaging-jackson.jar missing /META-INF/beans.xml file #2303

Closed
am-tribia opened this issue Sep 28, 2023 · 2 comments · Fixed by #2306
Closed

smallrye-reactive-messaging-jackson.jar missing /META-INF/beans.xml file #2303

am-tribia opened this issue Sep 28, 2023 · 2 comments · Fixed by #2306

Comments

@am-tribia
Copy link

am-tribia commented Sep 28, 2023

Why is smallrye-reactive-messaging-jackson.jar missing /META-INF/beans.xml file? I get the following error when I use
smallrye-reactive-messaging-jms:4.10.0 and smallrye-reactive-messaging-jackson:4.10.0

ERROR [io.sma.rea.mes.jms] (executor-thread-1) SRMSG15800: Unable to send message to JMS: java.lang.NullPointerException: Cannot invoke "io.smallrye.reactive.messaging.json.JsonMapping.toJson(Object)" because "this.jsonMapping" is null

Originally posted by @am-tribia in #2272 (comment)

@am-tribia am-tribia changed the title Why is smallrye-reactive-messaging-jackson.jar missing /META-INF/beans.xml file? I get the following error when I use smallrye-reactive-messaging-jackson.jar missing /META-INF/beans.xml file Sep 28, 2023
@ozangunalp
Copy link
Collaborator

I think those json modules didn't have beans.xml files to begin with. I am not sure why. Did your example work with 4.9.0 ?

@am-tribia
Copy link
Author

I think those json modules didn't have beans.xml files to begin with. I am not sure why. Did your example work with 4.9.0 ?

Nope, it didn't work in 4.9.0 either. I assume smallrye-reactive-messaging-jackson was a split from smallrye-reactive-messaging that had beans.xml.

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

Successfully merging a pull request may close this issue.

2 participants