Re: [aspectj-users] Serial Version Issue with AspectJ

[Andy Clement <andrew.clement@xxxxxxxxx>]

The serialversion UID for a type is based on the fields/methods within
it, weaving (particularly ITDs) can introduce new fields and methods
and so the serialversionuid changes.  The option -XaddSerialVersionUID
causes types (that implement serializable) to get a fixed
serialversionuid generated into them before they are modified by
weaving.

>  We have certain set of classes with SerialVersionUIDs in both Client and Server Library.

So you are manually setting the serialversionuid?  In that case you
don't need -XaddSerialVersionUID which is just about adding them where
they aren't specified.  There is no -XaddSerialVersionUID=false, just
don't supply it.  But are you saying that if you don't supply that
setting you are finding the value of your specified serialversionuid
for the class is changing after weaving?  AspectJ shouldn't be
touching any user supplied serialversionuid field...

There was a bug or two in -XaddSerialVersionUID many versions ago but
I think they were also resolved in around the 1.6.4/1.6.5 timeframe.

if you can give me a small code sample that shows what you mean, I'll
dig into it.

cheers,
Andy

On 30 July 2012 00:20, Jeevitha Muthusamy <mail2jeevithamk@xxxxxxxxx> wrote:
> Hi,
>
>  We have certain set of classes with SerialVersionUIDs in both Client and
> Server Library.
>  After Post AspectJ weaving, the UIDs in Server classes is modified.So, the
> Server and Client libraries conflict during server startup.
>
>  Does weaving modifies the class UIDs??
>  If so, Please let me know when and why the UIDs are modified and how can we
> resolve this issue??
>
>
>  Thanks,
> Jeevitha
>
> _______________________________________________
> aspectj-users mailing list
> aspectj-users@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/aspectj-users
>