[
https://issues.apache.org/jira/browse/FELIX-3064?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13079325#comment-13079325
]
David Humeniuk commented on FELIX-3064:
---------------------------------------
If BundleEvent is not intended to be serializable then why does it extend
EventObject which implements the Serializable interface? By inherently
implementing the Serializable interface it is in fact saying it is intended to
be serializable (at least by the contract of that interface). This contract
should force all implementers to make sure the realized class is serializable.
> BundleEvent is not serializable even though it extends EventObject which
> implements Serializable
> ------------------------------------------------------------------------------------------------
>
> Key: FELIX-3064
> URL: https://issues.apache.org/jira/browse/FELIX-3064
> Project: Felix
> Issue Type: Bug
> Components: Framework
> Affects Versions: framework-3.2.2
> Environment: Don't believe this is relavent but running on Linux
> (CentOS), Sun JVM 1.6.0.14
> Reporter: David Humeniuk
>
> When attempting to serialize BundleEvent, it trips up on serializing
> BundleImpl which would figure to be a member of BundleEvent. BundleImpl
> would either need to be serialiable or BundleEvent shouldn't try to serialize
> that actual member.
> This causes a problem for me since I'm using the EventAdmin service to post
> events through RMI. I would rather not have to put some ugly code that
> strips out things that say that are serialiable but really aren't.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
