Schema-registry: Warnings from Jersey when starting a RestApp
I'm including kafka-schema-registry:5.0.1-tests in a Java project.
Everytime I start a RestApp I get the following warnings (sorry for the Italian labels):
dic 12, 2018 11:32:16 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
AVVERTENZA: A provider io.confluent.kafka.schemaregistry.rest.resources.SubjectVersionsResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.kafka.schemaregistry.rest.resources.SubjectVersionsResource will be ignored.
dic 12, 2018 11:32:16 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
AVVERTENZA: A provider io.confluent.kafka.schemaregistry.rest.resources.SchemasResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.kafka.schemaregistry.rest.resources.SchemasResource will be ignored.
dic 12, 2018 11:32:16 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
AVVERTENZA: A provider io.confluent.kafka.schemaregistry.rest.resources.ConfigResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.kafka.schemaregistry.rest.resources.ConfigResource will be ignored.
dic 12, 2018 11:32:16 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
AVVERTENZA: A provider io.confluent.kafka.schemaregistry.rest.resources.CompatibilityResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.kafka.schemaregistry.rest.resources.CompatibilityResource will be ignored.
dic 12, 2018 11:32:16 AM org.glassfish.jersey.internal.inject.Providers checkProviderRuntime
AVVERTENZA: A provider io.confluent.kafka.schemaregistry.rest.resources.SubjectsResource registered in SERVER runtime does not implement any provider interfaces applicable in the SERVER runtime. Due to constraint configuration problems the provider io.confluent.kafka.schemaregistry.rest.resources.SubjectsResource will be ignored.
Some research led me to jersey/jersey#3700 and eclipse-ee4j/jersey#3700 but I couldn't figure out how to solve this inconvenience.
francescopellegrini
All 16 comments
Anyone..?
francescopellegrini
on 28 Feb 2019
Exactly the same here.
felipemmelo
on 11 Mar 2019
Same here
swardlincoln
on 19 Jun 2019
Same.
bowlofstew
on 12 Jul 2019
Still there in version 5.3.0
francescopellegrini
on 22 Jul 2019
Still present in v5.3.1
francescopellegrini
on 17 Sep 2019
Same here in version 5.3.0
marascha
on 30 Oct 2019
Still present in v5.3.2
francescopellegrini
on 8 Jan 2020
Still present in v5.4.0
francescopellegrini
on 15 Jan 2020
Still present in v5.4.1
francescopellegrini
on 5 Mar 2020
Still present in v5.5.0
francescopellegrini
on 24 Apr 2020
BTW the warning is issued by SchemaRegistryRestApplication.
francescopellegrini
on 7 May 2020
v5.5.1 has this too
martinhynar
on 19 Aug 2020
Still present in v6.0.0
francescopellegrini
on 25 Sep 2020
@francescopellegrini did you find a workaround? Looks like it prevents serializer from registering schemas, as endpoints do not work
green-creeper
on 22 Oct 2020
@green-creeper They are just warnings, they do not affect any functionality, as far as I know...
francescopellegrini
on 22 Oct 2020
Related issues
rocketraman
路
3Comments
IDispose
路
3Comments
twbecker
路
8Comments
phaas
路
5Comments
xiongtx
路
5Comments
Most helpful comment
Still there in version 5.3.0