i meant also to say that this should work in JBoss AOP
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3853441#3853441
Reply to the post :
http://www.jboss.org/index.html?module=bbop=postingmode=replyp=3853441
If a particular joinpoint is prepared you do not have to recompile or even shutdown
the JVM to add or remove an advice from a particular joinpoint. You can also
add/remove interceptors on a per instance basis at runtime with a prepared joinpoint.
How to prepare?
This will instrument the
In JBoss AOP you can attach things dynamically via the AspectManager class. You need
to prepare your class first:
http://www.jboss.org/wiki/Wiki.jsp?page=JBossAOP Go to Tutorial/Dynamic AOP
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3848186#3848186
Reply
Sorry I'm not able to look at this in very much detail right now.
Also, look at combining the .jar and .aop in an ear as shown in the tutorial. The
tutorial is by now means a complete guide to all possible packaging options, just
shows a few configurations I got working.
I have to admit I
Hi,
Before-After: There is more about this in another post somewhere in this thread, but
basically interception in JBoss AOP is both before and after.
Example:
| public class MyInterceptor implements Interceptor
| {
|public String getName() { return MyInterceptor; }
|
|
Thanks a lot.
After going through the documentation, I revisited my deployment to match what had
been speciifed but I still cant get it to work.
First, I created a .aop of my intercepter class (which I verified worked in the
stand-alone mode) :
| $ jar -tvf SimpleAOP.aop
| 0 Tue
Thanks Bill,
That was very informative.
Another query. AspectJ supports the notion of being able to define as to when you need
an advice to be executed - before or after. So far as my understanding goes, JBoss AOP
appears to be more interception based which appears to say ..when call X is
Sorry for replying to my own post.
Just another query. Would the interception for an EJB be different from that of a pure
Java class ?
Here is a test I tried.
- Created an entity bean with method findWithID(int) and deployed it in JBoss 3.2.5
following the instructions specified.
- I defined
Thanks Bill,
What do you mean by dynamic? I know that dynamic means different things in the AOP
world.. for instance AspectJ folks might say that their CFLOW is dynamic as it
collects information as the program is running yet is still to all intents and
purposes a compile time technique.
Why JBoss AOP over AspectJ?
- 100% pure Java
- annotation support (JDK 1.5 and 1.4)
- Metadata and annotation override facility
- load-time transformations (instead of compile time)
- hotdeployment of aspects (dynamic AOP)
- per-instance API (dynamic AOP)
- dynamic CFLOW
- pluggable pointcuts
-
I'm also interested in this. What are the major reasons for choosing JBoss AOP over
AspectJ or even Aspectwerkz?
View the original post :
http://www.jboss.org/index.html?module=bbop=viewtopicp=3843673#3843673
Reply to the post :
Bill is at Java One, and should be able to give a proper answer when he is back. In
the meantime:
Two people are working on Eclipse support at present, so expect something in that area
soon.
You can use JBoss AOP with 3.2.4 or higher, docs/misc/running_jboss.html in the
distribution shows
12 matches
Mail list logo
