[ 
https://issues.apache.org/jira/browse/CAMEL-10087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15348450#comment-15348450
 ] 

Daniel Kulp commented on CAMEL-10087:
-------------------------------------

I understand that.  

If my producer has is configured as:
{code}
....to("kafka:localhost:9999?topic=foo&serializerClass=com.dankulp.MySerializer")
{code}
then that path above will NOT find my serializer.   It is not in the Kafka 
jar/bundle.   It's in MY application bundle which is currently the context 
classloader.   Thus, if you set the context classloader to null, then the 
changes for  CAMEL-10069 are 100% necessary.

Have you tried without your patch but WITH the CAMEL_10069 changes?   Is it the 
partitioner that its having problems loading?   I think if you add:
{code}
"&partioner=org.apache.kafka.clients.producer.internals.DefaultPartitioner"
{code}
to the config, it may work.   For some reason, KafkaConfiguration isn't 
returning that default value for the partitioner like it is for the 
serializers.  


> camel-kafka does not work in OSGI container
> -------------------------------------------
>
>                 Key: CAMEL-10087
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10087
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-kafka
>    Affects Versions: 2.17.1
>            Reporter: Jay mann
>
> Currently this component is broken in OSGI environment due to this:
> https://issues.apache.org/jira/browse/KAFKA-3218
> We can leave it broken until they get their bugs worked out.  Or i can submit 
> a PR with an intermediate fix that should work, as described in the jira 
> noted above.
> https://github.com/apache/camel/pull/1049



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to