We would like our aspects to accumulate information, or self configure on a
PER_INSTANCE basis - then also make the instance and aspect stack serializable
in order to relocate it. Is this possible? A spike has shown that the aspects
dont get serialized is this a design feature or can we work
Thanks for the quick responses guys. I guess that might be the reason, and it
makes the sense but as a fundamental java concept it might also make the case
for it.
I mean conceptually speaking this raises the question of what is an object? The
more functionality you push to the aspects the mor
We have been developing an application that uses PER_INSTANCE scope aspects and
found the relative performance difference between PER_INSTANCE and PER_VM to be
2000 invocations/sec v 1,000,000 invocations/sec respectivley. (PER_JOINTPOINT
performance matched PER_INSTANCE). This overhead needs to
It would repeatedly reinitialize itself on every invocation because the
"initialized" flag wasnt being set. Net result was very slow performance when
using PER_INSTANCE scoping.
neil.
ps. I wasnt sure where to put this.
PerInstanceAdvice.java
public Object invoke(Invocation invocation) throw
performance went from 2,000/sec to around 2,000,000/sec - pretty dramatic.
HProf showed that init() is introspecting the class to interrogate its
attributes, methods etc. This also involves alot of string manip.
Any idea when the next release of jboss-aop will be ?
-neil
View the original post
