[JBoss JIRA] Commented: (NETTY-371) OSGi Manifest requires Bundle-BuddyPolicy for object deserialization

Trustin Lee (JIRA) jira-events at lists.jboss.org
Tue Jan 4 01:29:18 EST 2011


    [ https://issues.jboss.org/browse/NETTY-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572860#comment-12572860 ] 

Trustin Lee commented on NETTY-371:
-----------------------------------

Hmm, to make sure, do you propose to add the two lines to the manifest?

Eclipse-BuddyPolicy: registered
Eclipse-RegisterBuddy: org.jboss.netty

or the four?

Bundle-BuddyPolicy: registered
Eclipse-BuddyPolicy: registered
Bundle-RegisterBuddy: org.jboss.netty
Eclipse-RegisterBuddy: org.jboss.netty


> OSGi Manifest requires Bundle-BuddyPolicy for object deserialization
> --------------------------------------------------------------------
>
>                 Key: NETTY-371
>                 URL: https://issues.jboss.org/browse/NETTY-371
>             Project: Netty
>          Issue Type: Bug
>          Components: Core API
>    Affects Versions: 3.2.3.Final
>            Reporter: Brett Wooldridge
>            Assignee: Trustin Lee
>
> In order for object deserialization (by the ObjectDecoder) to work in an OSGi environment
> Netty's OSGi MANIFEST.MF needs to include a header like:
> DynamicImport-Package: *
> Without this header, when the ObjectDecoder attempts to load the class for a serialized
> object, it will be unable to find the bundle that exports that package.  The result is a
> ClassNotFoundException.
> With this header in the manifest, the OSGi container will search for any bundle that
> exports the package containing the requested class, and will use that bundle's classloader
> to load the class.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the netty-dev mailing list