You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It occurs to me that the junit ext ought to be applying the service loader pattern to KafkaCluster with container and in-vm implementations contributed from separate modules. The common code that relies on kafka server classes should looked at with a view to eliminating the dependency (mostly config constants IIRC). That way, if a user wanted to exclusively use the container-based implementation, they could avoid the kafka-server dependencies completely.
Like I say, I don't see any pressing need to do this now, but wanted to share the idea.
The text was updated successfully, but these errors were encountered:
k-wall
changed the title
Excellent point. I needed to read up. I found https://medium.com/@danismaz.furkan/difference-between-optional-true-optional-and-scope-provided-scope-7404ec24fb59 helpful.
Use service loader to find KafkaCluster implementations
Oct 25, 2023
It occurs to me that the junit ext ought to be applying the service loader pattern to KafkaCluster with container and in-vm implementations contributed from separate modules. The common code that relies on kafka server classes should looked at with a view to eliminating the dependency (mostly config constants IIRC). That way, if a user wanted to exclusively use the container-based implementation, they could avoid the kafka-server dependencies completely.
Like I say, I don't see any pressing need to do this now, but wanted to share the idea.
Originally posted by @k-wall in #206 (comment)
The text was updated successfully, but these errors were encountered: