Problem using a local interface on an EJB

[hirowla]

I'm having trouble accessing a local interface bean, and I'm not sure what I'm doing wrong. The error I'm getting when looking up the name is:
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException: org.jboss.ejb.plugins.local.LocalHomeProxy (no security manager: RMI class loader disabled)]
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:652)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:507)
at javax.naming.InitialContext.lookup(InitialContext.java:347)
(plus a heap more).

I'm using JBoss 3.2.3 (default configuration), JDK 1.4.2. Not sure what else would help, but let me know if anything can help. BTW, the EJB works well if you access it via the REMOTE interface. I'm using XDoclet to generate the interfaces, so I don't think it's a hand-coding mistake.

Thanks,

Ian

[juha]

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.

[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?

[juha]

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?

[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.

[hirowla]

I forgot to mention (if it matters) - I'm running JBoss through Eclipse (using JBossIDE 1.2.2).