AspectJ and EclipseStore

[fschon]

How does EclipseStore handle a AspectJ annotated bean? AFAIK AspectJ does some binary modifications to the class at runtime, and also in some cases at compile time. How does EclipseStore manage such a modified class? For e.g. can a AspectJ modified bean be stored and then read back in a non-AspectJ enabled environment?

[hg-ms]

We never tested AspectJ with EclipseStore, so we can’t guarantee that EclipseStore and AspectJ are compatible.
Nevertheless, here are some thoughts on this:

• As far as I know AspectJ does its modifications to classes at compile time or during class loading. EclipseStore analyses classes the first time a class gets persisted. As this is after loading the class, it should be possible to persist classed modified by AspectJ.
• Hot code swapping must not be done, as we will not recognize those modifications.
• If Load-Time Weaving is done it may be necessary to configure EclipseStore to use the correct class loader.
• The most critical modification a those done to the fields of a class (e.g. adding/removing/renaming)
• Reading back a persisted object that was modified by AspectJ into a non-AspectJ enabled environment can work because of the Legacy Type Mapping we do at startup.