| Re: [aspectj-dev] Stateful JoinPoints |
Eric Eide wrote:
"David" == David J Pearce <d.pearce@xxxxxxxxxxxx> writes: David> Well, the idea would be only to permit such state if the client David> in question explicitly requested it - e.g. by overriding the David> JoinPoint.StaticPart class. Are you suggesting that such overriding be allowed on a per-class/interface basis?
The idea would be allow the JoinPointStaticPartFactory (or whatever it is actually called) to return instances of some sub-class of JoinPoint.StaticPart. Does that make sense?
If not, that would seem to present a possible barrier to the reuse of classes across applications: one class might want one kind of derived static part, while a different class might want another.
Yes it seems unclear how multiple extensions would be managed. Perhaps it could be done on a per-aspect basis, although I'm very much uncertain if this is technically feasible.
Dave
If so, one might imagine other difficulties. For instance, if AspectJ allowed derived static part objects on a per-interface basis, what should AspectJ do for a class that implements two interfaces that request different derived static part objects? Eric.