The testsuite is nearly back at 100%
./build.sh test -Dtest=jca -Dnojars=t
./build.sh test -Dtest=jcaprops -Dnojars=t
The one remaining issue is the jboss-ra.xml parsing which I'm going to work on next
along with a tidyup of some other deployment issues.
While I was fixing the tests I changed some of the stress tests so they don't take
so long to run in normal operation and shortend the waits in the background validation tests.
A similar thing could be done with the prefill and ha connection tests but these
aren't too bad with the tests taking 30s and 1 minute respectively on my machine.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142802#4142802
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142802
Hi, Clebert!
anonymous wrote : Is there any hacks from javassist involved on calling the classLoader (direct calls to internal methods)?
Yes, Javassist calls defineClass method, which is internal to ClassLoader. look at the Javassist code that invokes defineClass method:
method.setAccessible(true);
| Class clazz = (Class)method.invoke(loader, args);
| method.setAccessible(false);
| return clazz;
|
anonymous wrote : Can you check if you are aways using the correct classloader?
The class loader we are using is the class loader that loaded the aspect class:
aspect.getClass().getClassLoader();
So that every class generated to interact with the aspect class is actually loaded by the same class loader that loaded the aspect class itself.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4142765#4142765
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4142765