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

Refactor registration of serialization once support is present in Quarkus #2755

Closed
JiriOndrusek opened this issue Jun 9, 2021 · 0 comments · Fixed by #2904
Closed

Refactor registration of serialization once support is present in Quarkus #2755

JiriOndrusek opened this issue Jun 9, 2021 · 0 comments · Fixed by #2904
Assignees
Milestone

Comments

@JiriOndrusek
Copy link
Contributor

JiriOndrusek commented Jun 9, 2021

Once following change is part of quarkus (quarkusio/quarkus#15380), usage of serialization configuration should be revisited and replaced with buildItems.

Currently there are 2 extensions using it: nitrite and sql.

Consider making automatic registration of basic types and of DefaultExchangeHolder with its hierarchy.

(Here is a branch with a try of such refactor without buildItems - https://github.com/JiriOndrusek/camel-quarkus/tree/sql-aggregator-core-changes-not-wanted)

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