OK, now I have made it work. I was not deploying the application as a full .ear file, I was deploying the interest.jar to jboss and running a separate servlet in Tomcat. I found that when you run in this configuration, the servlet does not automatically have classpath access to the EJB classes, so when it tries to instantiate the Home or Remote interfaces you get a ClassNotFound exception To make it work, you can deploy your application as a full ear file, with its .jar and .war elements and Jboss will automatically make your interfaces available to the servlet. Else if you prefer to run in a configuration where the servlets are deployed on their own (for development purposes, for example) you should manually make the interfaces available to the servlet by copying the InterestHome.class and Interest.class files to your classes directory in the corresponding webapps directory (under the correct path setup, com/web_tomorrow/interest/). Alternatively, if you copy the interest.jar to the /lib/ext/ directory of JBoss and restart it, it will make these clasess available to Tomcat and its servlets. I believe that you could also try to add the interest.jar lib to the Tomcat classpath, but I am not really sure how this is done Hope all this helps! Carlos _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
