Try putting your EJB project's jar file in the classpath on the client side (where you need to invoke the EJB).
Type: Posts; User: sureshk; Keyword(s):
Possible fix
Try putting your EJB project's jar file in the classpath on the client side (where you need to invoke the EJB).
Re: Fixed it
I saw this same issue in the project i'm working on. I jarred up my EJB project and put it in the client side classpath. It fixed this issue.