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

Support marshalling of JAXBElements in REST Client and Server Reactive #33924

Merged
merged 1 commit into from
Jun 9, 2023

Conversation

Sgitario
Copy link
Contributor

@Sgitario Sgitario commented Jun 9, 2023

I made also this change in the server, even though I think it's a niche use case here, but just to keep the server and client writers synced.

Also, I discarded the idea of returning JAXBElements which would be a more complex scenario.

Fix #33875

I made also this change in the server, even though I think it's a niche use case here, but just to keep the server and client writers synced. 

Also, I discarded the idea of returning JAXBElements which would be a more complex scenario. 

Fix quarkusio#33875
@quarkus-bot
Copy link

quarkus-bot bot commented Jun 9, 2023

✔️ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

@Sgitario Sgitario merged commit 42f5f1d into quarkusio:main Jun 9, 2023
@Sgitario Sgitario deleted the 33875_good branch June 9, 2023 09:54
@quarkus-bot quarkus-bot bot added this to the 3.2 - main milestone Jun 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

quarkus-rest-client-reactive-jaxb does not support direct marshalling of JAXBElement<T>
2 participants