-
1. Re: Problem using a local interface on an EJB
juha Feb 15, 2004 9:36 PM (in response to hirowla)Local interfaces only work "locally", that is, within the application server process space.
Attempting to lookup a bean that only has a local interface from another process will always fail. -
2. Re: Problem using a local interface on an EJB
hirowla Feb 15, 2004 10:19 PM (in response to hirowla)I am aware of this. I'm attempting to unit test the Bean using Cactus (for in-container testing if you are unaware). So I should be able to access the local interface, shouldn't it?
-
3. Re: Problem using a local interface on an EJB
juha Feb 15, 2004 11:08 PM (in response to hirowla)What is the server side component cactus deploys on JBoss? How is that component trying to access the local interface; does it package its own jndi.properties, how does it integrate with the classloaders?
-
4. Re: Problem using a local interface on an EJB
hirowla Feb 16, 2004 3:46 PM (in response to hirowla)I'm not 100% sure of what it does. But cactus is in essence a servlet application (I'm deploying it as a WAR file). The jndi.properties file is packaged with the web application. Don't think it does anything special with classloaders - I think it lets JBoss handle that.
-
5. Re: Problem using a local interface on an EJB
hirowla Feb 17, 2004 5:27 AM (in response to hirowla)I forgot to mention (if it matters) - I'm running JBoss through Eclipse (using JBossIDE 1.2.2).