Stub classes must be included when using remote Enterprise JavaBeans (EJB) 2.x

A client must include stub classes when you start a remote EJB bean that is hosted on WebSphere Application Server. In some cases, if the client is WebSphere Application Server, the product automatically generates the correct stub classes:

• If a client application starts a remote EJB bean that is contained within the same application, WebSphere Application Server Liberty automatically generates stub classes.
• If the target EJB bean is running in a separate application and uses the EJB 2.x remote programming model with the EJBHome and EJBObject interfaces, then the client must include stub classes on its classpath. If the EJB is hosted on WebSphere Application Server traditional, you can copy the EJB client JAR file from the application in the EAR file after it is processed by the ejbdeploy command. If the EJB is hosted on Liberty, you must use the rmic program that is included with your Java 8 software development kit (SDK) from the WebSphere Application Server traditional client to generate the stub classes for the target EJB bean, and then you must include the stub classes with the client.
• If the target EJB is running in a separate application and uses the EJB 3 remote programming model, then the client WebSphere Application Server traditional or Liberty process automatically generates stub classes. EJB components that use the EJB 3 remote programming model on Liberty can be remotely accessed by WebSphere Application Server or WebSphere Application Client processes only.

For more information, see Using Enterprise JavaBeans (EJB) with remote interfaces on Liberty.