This is probably not a JBOss AOP problem, but rather how you've packaged your classes in WLS.
Seems like some bug in weblogic PortableRemoteObject implementation or their JNDI.
I could get it to work in JBoss 3.2.3
You could get it to work on JBoss 3.2.3? Where do you place your interceptor? For example, if I want to intercept the method invocation of com.xyz.zmedrec.PhysicianSessionEJB with the interceptor interceptor.TestMethodInterceptor as indicated in the folloiwng jboss-aop.xml:
<?xml version="1.0" encoding="UTF-8"?>
I AOPized a session EJB in a sample WebLogic 8.1 application. And I put the interceptor directory under the same parent directory as that of com sub-directory of the sample application. When I tested the AOPized application, the TestMethodInterceptor wasn't invoked. From the console log, I can see the invoked sessionEJB was indeed AOPized.
Can anyone please tell me where I should place my interceptor?
Here is the operatiing environment:
OS: Window XP.
Thanks in advance.
You'll have to tell me your exact setup and steps you made to do things.
1. Did you precompile your clases with aopc?
2. Did you set the System Property jboss.aop.path?
You'll have to follow the JBoss AOP for standalone instructions when working with Weblogic.
Set the system property jboss.aop.path=<xml file> in your startweblogicserver script and in addition you may have to add the jboss-aop.jar and javassist.jar to the classpath. The interceptor jars will have to be added to the classpath as well. Otherwise if you want something more sophisticated you could create some URL classloading utility that would dynamically load the interceptor jars.