|Instances going out of scope [message #61917]
||Thu, 16 February 2006 11:15
Originally posted by: ytgyazilim.gmail.com|
A have long been aware of AspectJ but never really had to / time to look
into it so far.
Now that I have a project that fits perfectly as a use case for aspects,
I am looking into it, and amazed with the outcome of the project.
I started with JBOSS - IDE aop components and was quite a
disappointment. I started with AJDT with low expectations and waow. I
think I got what I need. Very well done folks.
I have a couple of questions:
1) Is it possible to maintain some meta information in a call stack that
the original call stack does not have and need.
What I mean by that is
a) attaching some kind of meta information in pointcut 1.
b) checking if we have this meta info in pointcut 2.
pointcut 2 may / may not have no idea about pointcut 1 and takes an
action to metadata state
A Real example is I would like to wrap existing calls to the server with
ShowBusyCursorWhile method of progress service.
if we are already executing in the progress service then get a hold of
the monitor parameter and just create a sub task on that.
2) Is there a way to pointcut variables going out of scope.
A use case for that to make sure to remove a stateful EJB bean if
it goıes out of scope.
Thanks very mush in advamce and keep up the good work.
Powered by FUDForum
. Page generated in 0.04271 seconds