Yes, as soon as possible.
I forget to mention that this behaviour happens with jboss-aop-2.0.0.GA. Using
jboss-aop_1.5.6.GA it's all okay (apart from other problems using hotswap and
the javaassist library bundled with this version :) )
View the original post :
http://www.jboss.com/index.html?m
Hi,
if I have a class with an enclosed class like this
Class POJO {
private String aField;
...
class AnotherClass {
public void someMethod() {
aField = "something";
}
}
}
and I add an aspect at runtime through these instructions:
AdviceBinding binding = new AdviceBinding("execution(publi
I tried to simulate the situation described with this simple example:
the classes in filesystem are:
DynamicAOP/bin/AspectCreator.class
DynamicAOP/bin/AspectCreator$MyThread.class
DynamicAOP/bin/Caller.class
DynamicAOP/SimpleAspect.class
The classpath points to DynamicAOP/bin/ so that SimpleAs
I have some questions:
1) if I want to prepare some classes for dynamic aop I have to put the @prepare
("all(this)") annotation in all classes or putting it in the main class is
enough?
2) I need a facility like the hot deployment of JBoss where if an aspect is
inserted in a specified director
Now I'm using jboss-aop-2.0.0.GA and running the application with
run-load15HotSwap.sh.
I've this exception:
java.lang.NullPointerException
at org.jboss.aop.pointcut.MethodMatcher.(MethodMatcher.java:72)
at
org.jboss.aop.pointcut.ExecutionMethodMatcher.(ExecutionMethodMatcher.java
I tried to reproduce the situation when AspectManager.addBinding(); blocks and
I found the same problem:
*** Caller.class ***
import org.jboss.aop.Prepare;
@Prepare("all(this)")
public class Caller {
private AspectCreator ac;
public Caller() {
System.out.
Hi,
In my app I need to deploy aspects received from the network at runtime...
I'm trying to use hot deploy facilites of jboss-aop but something goes wrong.
Here it is a snippet of my code:
AdviceBinding binding = null;
try {
binding = new AdviceBinding("exec
