I have the same problem.
Maybe you have now the solution, would you tell me?
I solved it putting some JBoss JARs in the CLASSPATH , that weren't there before .
The JARs I use are :
Hope it helps someone
I had the same issue, and ensuring that the proper files you mentioned are part of my local classpath did solve the issue.
My concern is that this may be just a 'kludge' around an another issue. The exception message:
javax.naming.CommunicationException [Root exception is java.lang.ClassNotFoundException:
org.jboss.proxy.ClientContainer (no security manager: RMI class loader disabled)]
is troublesome. Looks like the JBoss server was trying to send the org.jboss.proxy.ClientContainer class over RMI, and because of some 'local' security manager established that it didn't have permission to load it, it just threw the exception.
I did set a SecurityManager in my code (I tried both SecurityManager and RMISecurityManger), with a security policy file to be 'wide opened'. Still, I had to set my classpath according to your suggestion.
Could it be that JBoss server 'forgot' to include the proper jar files in the codebase?
Just wandering, and would love not to have to make these files part of my 'local' classpath.
PS: I'm running on WinNT, under Netbeans 3.4, using JBoss 3.04_tomcat_4.1.12