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 JMS ObjectMessage #2919

Merged
merged 1 commit into from Jul 21, 2021

Conversation

jamesnetherton
Copy link
Contributor

No description provided.

@jamesnetherton
Copy link
Contributor Author

Having dug into the serialization support code a bit more. I think my docs are a bit misleading. In this case, there's actually no need for users to explicitly enable it via the config property because the extension(s) produce CamelSerializationBuildItem. I'll amend the wording...

@jamesnetherton
Copy link
Contributor Author

Latest commit fixes the wording of the documentation to something that more accurately describes the serialization support.

Copy link
Contributor

@ppalaga ppalaga left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks looks good, two more questions inline.

@jamesnetherton
Copy link
Contributor Author

Latest commit adds the org.w3c.dom.Node statement to SJMS & SJMS2 docs (I mistakenly thought those components did not support it).

@ppalaga
Copy link
Contributor

ppalaga commented Jul 21, 2021

Perfect, thanks!

@jamesnetherton jamesnetherton merged commit 10197de into apache:main Jul 21, 2021
@jamesnetherton jamesnetherton deleted the jms-object-message branch July 21, 2021 12:12
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 this pull request may close these issues.

None yet

3 participants