geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder (JIRA)" <...@geronimo.apache.org>
Subject [jira] Updated: (GERONIMO-644) Serialized form of GBeans objects must each declare SUID
Date Sat, 27 Aug 2005 01:53:05 GMT
     [ http://issues.apache.org/jira/browse/GERONIMO-644?page=all ]

Aaron Mulder updated GERONIMO-644:
----------------------------------

    Fix Version: 1.0
    Description: 
Since Geronimo exchanges config information via serialized form of Java objects, its imperative
that the serializable classes declare a serialVersionUID.  If they don't then the serialized
form is not necessarily compatible across Java implementations (or even Java compilers) [1].

The case in point is the wire format classes in ActiveMQ (e.g. "org.codehaus.activemq.message.DefaultWireFormat")
which are marked serializable and do not declare a static ID.  I've tried raising this with
ActiveMQ [2] but without success.

I can provide the required SUID in each case, but it looks like I might need help to get it
into the ActiveMQ code.

[1] http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100
[2] http://article.gmane.org/gmane.comp.java.activemq.devel/486

  was:
Since Geronimo exchanges config information via serialized form of Java objects, its imperative
that the serializable classes declare a serialVersionUID.  If they don't then the serialized
form is not necessarily compatible across Java implementations (or even Java compilers) [1].

The case in point is the wire format classes in ActiveMQ (e.g. "org.codehaus.activemq.message.DefaultWireFormat")
which are marked serializable and do not declare a static ID.  I've tried raising this with
ActiveMQ [2] but without success.

I can provide the required SUID in each case, but it looks like I might need help to get it
into the ActiveMQ code.

[1] http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100
[2] http://article.gmane.org/gmane.comp.java.activemq.devel/486

    Environment: 

This is going to be a vast job -- I think it would ultimately be easier to reduce our reliance
on serialization.  However, if we go forward with serialization for 1.0, we ought to seriously
consider this to facilitate upgrades and so on.

If we decide this is too much work but can't replace serialization, perhaps we can eliminate
the serialized state in favor of the ManageableAttributeStore, and include the original plan
in the config store.  Then in an upgrade scenario we'd export all the plans and the ManageableAttributeStore
file, upgrade the server components, restore the ManageableAttributeStore file, and redeploy
all the plans.  This would be hard but potentially less work than tracking down and altering
every relevant Serializable object.

> Serialized form of GBeans objects must each declare SUID
> --------------------------------------------------------
>
>          Key: GERONIMO-644
>          URL: http://issues.apache.org/jira/browse/GERONIMO-644
>      Project: Geronimo
>         Type: Bug
>     Reporter: Tim Ellison
>     Assignee: Jeremy Boynes
>      Fix For: 1.0

>
> Since Geronimo exchanges config information via serialized form of Java objects, its
imperative that the serializable classes declare a serialVersionUID.  If they don't then the
serialized form is not necessarily compatible across Java implementations (or even Java compilers)
[1].
> The case in point is the wire format classes in ActiveMQ (e.g. "org.codehaus.activemq.message.DefaultWireFormat")
which are marked serializable and do not declare a static ID.  I've tried raising this with
ActiveMQ [2] but without success.
> I can provide the required SUID in each case, but it looks like I might need help to
get it into the ActiveMQ code.
> [1] http://java.sun.com/j2se/1.3/docs/guide/serialization/spec/class.doc6.html#4100
> [2] http://article.gmane.org/gmane.comp.java.activemq.devel/486

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message