> On second thoughts, making them transient may not be a good idea because the
> deserialization may fail.
> Do you think you can make JoinPoint.StaticPart and its contents
> Serializable? I am not sure if that would be correct, but just asking.
> Or, is there any option to weave the classes so that the synthetic fields do
> not exist at all?
> I know that I'm asking for something that may not be a requirement for most
> usage scenarios or the actual intended usage of AspectJ. But I am stuck with
> this problem and just checking if there is a way out.
> Thanks for your time.
> On Wed, Feb 29, 2012 at 4:39 PM, Andy Clement <andrew.clement@xxxxxxxxx
>> I can provide you an option to make them transient, but I'm hesitant
>> to just change the default to transient. If you want an option like
>> that, please open a bugzilla:
>> and I'll take a look.
>> On 28 February 2012 14:35, Choudary Kothapalli
>> > My product MaintainJ uses AspectJ load time weaving to capture the call
>> > trace at runtime. When weaving an application, the following exception
>> > is
>> > seen.
>> > Caused by: java.io.NotSerializableException:
>> > org.aspectj.runtime.reflect.JoinPointImpl$StaticPartImpl
>> > at java.io.ObjectOutputStream.writeObject0(Unknown Source)
>> > at java.io.ObjectOutputStream.writeObject(Unknown Source)
>> > at xxx.yyyyy.ZZZClass.writeExternal_aroundBody4(ZZZClass.java:70)
>> > AspectJ LTW seems to insert many fields as below in the class files and
>> > serializing them seems to be failing.
>> > private static final org.aspectj.lang.JoinPoint.StaticPart ajc$tjp_0; /*
>> > synthetic field */
>> > Is there any quick fix for this? Can AspectJ make these fields transient
>> > without any other issues?
>> > Thanks,
>> > Choudary Kothapalli
>> > MaintainJ Inc.
>> > _______________________________________________
>> > aspectj-dev mailing list
>> > aspectj-dev@xxxxxxxxxxx
>> > https://dev.eclipse.org/mailman/listinfo/aspectj-dev
>> aspectj-dev mailing list
> aspectj-dev mailing list
aspectj-dev mailing list