Deploying Remote EJB and Web Application

I have successfully deployed the EJB 3 module and the JSF WEB application that calls the beans EJB module using the netbeans local area network. Now, when I try to deploy this in an intermediate environment, I get the following error:

root cause
javax.servlet.ServletException: com.sun.enterprise.InjectionException: Exception attempting to inject Unresolved Ejb-Ref com.store.managedbeans.CustomerManagedBean/ customerService@jndi : com.store.service.CustomerRemote@null @ com.store.service.CustomerRemote@Session @null into class com.store.managedbeans.CustomerManagedBean
root cause javax.naming.NameNotFoundException: com.store.service.CustomerRemote#com.store.service.CustomerRemote not found

I deployed the EJB module and web application to glassfish v2 (in an intermediate environment). The EJB module box is located inside the WEB-INF / lib folder of the web application. It appears that the web application cannot find the EJB module. Classes are annotated using @Remote. And I call the interfaces, not the bean, using @EJB. And of course, it worked when I deployed it under Netbeans.

+4
source share
1 answer

From the comments:

The EJB module referenced the JSE Queue Connection Factory. The resource was not created on the staging server. Although the EJB module was allowed for deployment, the JNDI log from the console shows that none of the EJBs were associated with any names due to a problem when deploying the module.

0
source

Source: https://habr.com/ru/post/1312281/


All Articles