You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@thrift.apache.org by "Ioannis Canellos (Commented) (JIRA)" <ji...@apache.org> on 2011/12/24 11:00:30 UTC

[jira] [Commented] (THRIFT-184) Add OSGi Manifest headers to the libthrift java library to be able to use Thrift in the OSGi runtime

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

Ioannis Canellos commented on THRIFT-184:
-----------------------------------------

Good work!

A proper manifest is the first step required in order to enjoy thrift inside OSGi.
However, I can see issues with the extensive use of Class.forName() in thrift, which is an approach that don't actually promotes modularity.

Ideally, a way for the user to specify the class loader that will be used for loading classes would solve this.
An alternative would be to add a fallback to the thread context class loader.
                
> Add OSGi Manifest headers to the libthrift java library to be able to use Thrift in the OSGi runtime
> ----------------------------------------------------------------------------------------------------
>
>                 Key: THRIFT-184
>                 URL: https://issues.apache.org/jira/browse/THRIFT-184
>             Project: Thrift
>          Issue Type: New Feature
>          Components: Java - Library
>            Reporter: Siamak Haschemi
>            Assignee: Jake Farrell
>            Priority: Trivial
>             Fix For: 0.9
>
>         Attachments: bnd-0.0.249.jar, libthrift.bnd, osgi.patch, thrift-184.patch
>
>   Original Estimate: 10m
>  Remaining Estimate: 10m
>
> To be able to use Thrift in the OSGi runtime (see http://en.wikipedia.org/wiki/OSGi), some additional Manifest entries are needed. The bnd-tool (see http://www.aqute.biz/Code/Bnd) creates this entries automatically.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira