geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Ellison (JIRA)" <>
Subject [jira] Commented: (GERONIMO-644) Serialized form of GBeans objects must each declare SUID
Date Mon, 16 May 2005 09:20:32 GMT
     [ ]
Tim Ellison commented on GERONIMO-644:

There is a handy Eclipse compile time check for "Serializable class without serialversionUID",
which would catch them all at compile time, but for now here's a couple I found with a runtime
test bringing up bin\server.jar on 1.0-M3.

The class org.codehaus.activemq.message.DefaultWireFormat does not declare an SUID.
To retain compatibility with existing persistent form it should declare:
  static final long serialVersionUID =-8707485428936851184L;
There is a serializable class hierarchy rooted at org.apache.geronimo.gbean.GAttributeInfo
that does not declare a SUID.

Bringing up the bin\server.jar exposed:
which to retain compatibility with existing persistent forms should declare
  static final long serialVersionUID =-3766690289494192629L;

> Serialized form of GBeans objects must each declare SUID
> --------------------------------------------------------
>          Key: GERONIMO-644
>          URL:
>      Project: Geronimo
>         Type: Bug
>     Reporter: Tim Ellison
>     Assignee: Jeremy Boynes

> 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)
> 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]
> [2]

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message