You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Doug Cutting (JIRA)" <ji...@apache.org> on 2014/01/03 19:27:56 UTC
[jira] [Commented] (AVRO-1425) Fallback to thread context class
loader in SpecificData.getClass()
[ https://issues.apache.org/jira/browse/AVRO-1425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861749#comment-13861749 ]
Doug Cutting commented on AVRO-1425:
------------------------------------
I'd prefer we fix this more generally, as in AVRO-987. Let me see if I can revive that patch.
> Fallback to thread context class loader in SpecificData.getClass()
> ------------------------------------------------------------------
>
> Key: AVRO-1425
> URL: https://issues.apache.org/jira/browse/AVRO-1425
> Project: Avro
> Issue Type: Improvement
> Components: java
> Affects Versions: 1.7.5
> Reporter: Bertrand Delacretaz
> Priority: Minor
> Attachments: AVRO-1425.patch
>
>
> While trying to implement a simple Avro serializer that works in an OSGi environment I stumbled on the fact that SpecificData.getClass() only uses its own ClassLoader. Letting it fallback to the thread context class loader (TCCL) makes it more OSGi-friendly, as callers can then set the TCCL as needed.
> AVRO-987, which hasn't been applied and is now stale, is about making Avro fully OSGi compliant and would fix my issue as well, but I tried to aim for the minimal changes that work for me (patch follows).
> My use case is at https://github.com/bdelacretaz/avro-osgi-test - at commit e3b4c47839 there my test passes with the attached patch applied to avro trunk revision 1552851.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)