0 Replies Latest reply on Sep 5, 2003 5:22 AM by gpower

    Session Bean access in 4.0.0DR2

    gpower Newbie

      Hi All,

      When I try to access a session bean remotely on the developer release 2 server I notice that the client test says "Starting Axis SOAP Connector" after which it throws a javax.naming.CommunicationException and promptly fails.

      The test appears to get the intial context ok but fails trying to get a reference to the deployed session bean (which has deployed, it shows up in the JNDI view on the jmx-console).

      I have managed to get the test to connect in some way to the session bean by throwing quite alot of additional jars (the Apache Axis jars) into the client classpath, but I was hoping that someone could enlighten me and explain how DR2 differs from the 3.x series with regard to such a situation.

      I have dug around on the forums and mailing list and suspect that this is probably a result of the introduction of the new remoting subsystem, but I would really appreciate it if someone could tell me how to configure the server to use the 'old' transport/connection mechanism.

      Any help would be much appreciated!