Tomcat as the client has to be considered as a client which does not run in the same application server container. So you have to package all relevant classes/interfaces into the .war file which is deployed on Tomcat.
Looking at the stack trace: The JBoss server does respond, it's the JBoss client who reports that a class is missing:
The actual error (missing class) is packaged in a NamingException.
So you have to put the relevant classes into the .war file for Tomcat: It's probably your remote interface recc.business.login.LoginBeanRemote.
I always have EJB classes (implementation) and their interfaces in two separate packages, and the EJB client gets a .jar file which just contains the interfaces (and possibly exceptions). So a .jar consisting of interfaces and possibly exceptions gets packaged into the .war for the client.
Generally speaking these items have to be checked, if a stand-alone client fails to work
Are the remote interfaces in the class path?
Are the properties for the InitialContext complete?
Is the JNDI name correct? And is that JNDI name really visible from the client?
final Properties initialContextProperties = new Properties();
// See .../jboss-7/standalone/configuration/application-users.properties
Great answer, thank you. I forgot to add the jar file to my classpath and I put the LoginBeanRemote in a package with a different name than the ejb-project. Unfortunately I still can't run the ejb. Can you take a look on my updated question?
I am not sure if your JNDI name builder is correct (distinctName is empty, so there is a "//" somewhere, and if the "ejb:" scop is visible for a remote client. Please have a look at JNDI Lookup on JBoss AS 6.0. This is applicable as well to JBoss 7, so try "java:global/...", because this scope is globally visible. And double check that the JNDI name you use turns up in the JBoss admin console as well. Please add the method of the EJB you are calling.
The "//" works on my console client and is also mentioned in official jboss documentation. I tried "java:global/.." It's causing an error, that "java:global" is not bound to the context, do you have any Idea what's missing? BTW: I have no EAR file in my deployment folder, I just deploy the .jar file
Is jboss-ejb-client.properties really in the class path of the .jar for Tomcat?
Have a look at JBoss AS7 JNDI ref. Instead of "Remote JNDI using ejb:" try "Remote JNDI using remote:". This explains as well the problems you have had and you are having now.