[jboss-jira] [JBoss JIRA] Resolved: (JGRP-1064) Serialization untidiness in AuthToken

[Bela Ban (JIRA)]

     [ https://jira.jboss.org/jira/browse/JGRP-1064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban resolved JGRP-1064.
----------------------------

    Resolution: Done


AuthToken is marshalled using only Streamable; Java serialization is not used. I added serialVersionUIDs anyway, but you can exclude AuthToken and subclasses from your checks

> Serialization untidiness in AuthToken
> -------------------------------------
>
>                 Key: JGRP-1064
>                 URL: https://jira.jboss.org/jira/browse/JGRP-1064
>             Project: JGroups
>          Issue Type: Bug
>    Affects Versions: 2.6.12
>            Reporter: Brian Stansberry
>            Assignee: Bela Ban
>            Priority: Minor
>             Fix For: 2.6.13, 2.8
>
>
> The abstract AuthToken class implements Serializable, so the AS serialization compatibility tests are monitoring it for incompatible changes. Per JBAS-7265 looks like one has crept in:
> FAIL: serialVersionUID error for org.jgroups.auth.AuthToken, 500 3079597723572751028, current: -2876389454499198917 
> This is minor, since JGroups presumably uses Streamable to marshal/unmarshal these. But some tidy up would be good:
> 1) The AuthToken.auth field should be transient since AUTH is not serializable.
> 2) A serialVersionUid field should be added to AuthToken and all subclasses.
> Do these classes need to be Serializable? If not, perhaps remove that in 3.0?

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