Add @Serial annotation

[gnodet]

No description provided.

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run

• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

• You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

• Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

• ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[orpiske]

@gnodet @davsclaus @oscerd sorry for my ignorance here ... serialization has never been my thing, so: is this still something we need?

[davsclaus]

not as much anymore - we do not recommend serializing java objects and sending them over the wire - a few old components still have an option to do that like JMS with transferExchange=true|false

[gnodet]

@gnodet @davsclaus @oscerd sorry for my ignorance here ... serialization has never been my thing, so: is this still something we need?

No, this is a compile time annotation which helps detecting issues in serialization related code. This is very similar to @Override which is not required, but helps the compiler raising issues in case of problems.

[orpiske]

@gnodet @davsclaus I wonder if we should just go ahead and remove all this serialization stuff. If it's something old, unused (and very likely unsafe), I don't see the point of having this in the code base.

[orpiske]

not as much anymore - we do not recommend serializing java objects and sending them over the wire - a few old components still have an option to do that like JMS with transferExchange=true|false

Oh, ok. Now I got it. I think we can't remove these without breaking backwards compatibility.

Thanks for the explanation @gnodet and @davsclaus