Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[aspectj-users] Serial Version UID

Hello,

the FAQ states:

"However, changes to the serialVersionUID attribute are typically only
important when using serialization for the long-term persistence of objects.
Using standard Java serialization for long-term persistence has a number of
drawbacks and many developers already use alternative solutions. For one
possibly standard solution, see Lon g-Term Persistence for JavaBeans
Specification."

I think that is only party true. This issue is really important for client -
server applications
depending on object serialization (RMI, EJB etc.). I would not call it
long-term persistence. Introducing
aspects on client or server side without breaking serial version UID is very
important in my opinion. 
Now with using byte-code weaving would'nt it be easy to provide a feature
that can handle serialVersionUID
a better way? For example having a flag that introduces a serialVersionUID
field with the value of original 
class (Either with warnings if there were introductions or ommitting such
classes)?

It would be great if such a thing could be integrated into the final 1.1
release.

Thanks,
Vincenz



Back to the top