You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Bertrand Delacretaz (JIRA)" <ji...@apache.org> on 2014/01/09 17:32:53 UTC
[jira] [Commented] (AVRO-987) Make Avro OSGi ready
[ https://issues.apache.org/jira/browse/AVRO-987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13866758#comment-13866758 ]
Bertrand Delacretaz commented on AVRO-987:
------------------------------------------
Thanks [~cutting], with your updated patch my OSGi tests (https://github.com/bdelacretaz/avro-osgi-test) pass. They fail on an unpatched Avro trunk.
My tests only use basic serialization/deserialization and IPC mechanisms, but for these use cases the patch helps.
> Make Avro OSGi ready
> --------------------
>
> Key: AVRO-987
> URL: https://issues.apache.org/jira/browse/AVRO-987
> Project: Avro
> Issue Type: New Feature
> Components: java
> Reporter: Ioannis Canellos
> Fix For: 1.7.6
>
> Attachments: AVRO-987-1_6_3-patch.txt, AVRO-987-patch-updated.txt, AVRO-987-patch.txt, AVRO-987.patch
>
>
> It would be really nice to be able to use Avro inside OSGi. To achieve this two things are required:
> i) Provide proper MANIFEST.MF.
> ii) Deal with potential class loading issues. Avro uses Class.forName a lot and that is not very OSGi friendly.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)