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

Avoid usage of static for Camel Kafka Connector catalog #588

Merged
merged 1 commit into from
Oct 14, 2020

Conversation

apupier
Copy link
Contributor

@apupier apupier commented Oct 14, 2020

it will allow to use several version of the catalog in the same JVM.

Signed-off-by: Aurélien Pupier apupier@redhat.com

it will allow to use several version of the catalog in the same JVM.

Signed-off-by: Aurélien Pupier <apupier@redhat.com>
@apupier apupier force-pushed the avoidStaticInConnectorCatalog branch from a9bf165 to a5b1f72 Compare October 14, 2020 08:02
Copy link
Contributor

@oscerd oscerd left a comment

Choose a reason for hiding this comment

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

Not a problem, but why do you need multiple catalogs in the same JVM? The embedded catalog is static by definition.

@apupier
Copy link
Contributor Author

apupier commented Oct 14, 2020

Given that I added the possibility to add/remove connector, the Catalog is dynamic and is not handling only embedded connector definitions.

for right now, to be able to write tests with different catalog more easily

for the future:

  • to allow handle several version of Camel Kafka Connector in the tooling
  • to let users provide their own connector definition

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.

2 participants