1 Reply Latest reply on Apr 22, 2006 8:40 PM by Mark Lybarger

    dynamic class loading

    chaitanya Novice

      i have war (in this JSP TagHandler class trying to look up EJB business method that is in ear deployed in node2 instance) deployed in jboss/node1 instance..

      ear deployed in jboss/node2 instance..

      in the WAR i have added only home and remote interfaces in WEB/classes at client side .(Do i need other custom classes which are using by EJB in WAR);

      how do i enable dynamic class loading at client side;i am using jboss-4.0.2;if i enable dynamic class loading do i still need to drop home and remote interfaces and custom classes at client side.

      in run.bat at client side.. what steps shouild i take to enable dynamic class loading to look up classses at server side.

      set JBOSS_CLASSPATH=C:/jboss-4.0.2/client/jbossall-client.jar -Djava.security.manager=java.rmi.RMISecurityManager

      Hashtable contextProperty = new java.util.Hashtable();
      contextProperty.put(Context.INITIAL_CONTEXT_FACTORY, "org.jnp.interfaces.NamingContextFactory");
      contextProperty.put(Context.PROVIDER_URL, "jnp://localhost:1099");

      InitialContext context = new InitialContext(contextProperty);
      DocumentSessionHome home = (DocumentSessionHome)context.lookup("DocumentSessionBean");
      DocumentSession doc =(DocumentSession)home.create();

        • 1. Re: dynamic class loading
          Mark Lybarger Apprentice

          have you tried it and encountered an error?

          dynamic class loading should just work unless you've taken steps to configure your server otherwise.

          i've had numerous remote clients to ejb's that only have the ejb-client jar's and the jboss client jar's in their classpath. i am under the impression that the client downloads the classes that implement the home and remote component interface.

          i suppose i could turn off the class downloading service and see how that works. the service could be a slight security risk, as it exposes your login-config.xml by default over http...