commons-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Klein (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LANG-1049) SerializationUtils.deserialize() can not be used within OSGi
Date Fri, 20 Feb 2015 13:42:11 GMT

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

Marcus Klein commented on LANG-1049:
------------------------------------

My alternative option is currently NOT to use SerializationUtils.deserialize(). In my eyes
this is not an alternative option.

Please add as feature request, what Joerg describes. But I personally don't see this as a
feature request. The purpose of org.apache.commons.lang is to provide utilities for easier
Java coding. Furthermore org.apache.commons.lang is exposed as being compatible with OSGi.
But as described here, the utility is not usable in OSGi because of framework/classloader
restrictions. If org.apache.commons.lang would not be exposed as OSGi compatible, this would
be a feature request, of course. In this case it is a bug.

> SerializationUtils.deserialize() can not be used within OSGi
> ------------------------------------------------------------
>
>                 Key: LANG-1049
>                 URL: https://issues.apache.org/jira/browse/LANG-1049
>             Project: Commons Lang
>          Issue Type: Bug
>          Components: lang.*
>    Affects Versions: 2.6
>         Environment: Equinox
>            Reporter: Marcus Klein
>            Priority: Blocker
>
> SerializationUtils.deserialize() throws a SerializationException if objects should be
deserialized that can not be resolved by OSGi classloader of org.apache.commons.lang bundle.
> To solve this problem I suggest to allow buddy classloading within commons.lang to allow
other bundles to register their class loaders.
> Please add
> Eclipse-BuddyPolicy: registered
> to the MANIFEST.MF of commons.lang to solve this problem.



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

Mime
View raw message