What is local/remote and no-interface view in EJB?

by

Remote client view

When your EJB and its clients will be in a distributed environment – meaning EJBs and clients will reside on separate Java virtual machines. Example : EJBs hosted on a WebSphere Application Server and Servlets that consume EJB APIs hosted on a Tomcat server.

Local client view

Only when it is guaranteed that other enterprise beans or clients will only address the bean within a single JVM. Example, EJBs as well as the Servlets deployed on the same WebSphere server.

No-Interface view

Is almost same as local client view, but there are differences. Your bean class is not required to implement client view interfaces in this case. All public methods of the bean class are automatically exposed to the caller. no-interface view always acquires an EJB reference – just like local or remote views – either through injection or JNDI lookup; but, Java type of the EJB reference is the bean class type rather than the type of a local interface. This is a convenience introduced as part of Java EE6.

Difference between local client view and no-interface view

In case of no-interface view, the client and the target bean must be packaged in the same application (EAR). In case of local view, client can be packaged in a separate application than the enterprise application. So, this gives more flexibility in terms of fine-graining your components.

You may use local client view vs no-interface view depending on your API usage scenario. It is very likely for no-interface view to receive flexible features in future specs.

Reason

Historically or otherwise, a client wishing to use EJB services was supposed to “look up” the bean on the container ( with certain initial contexts ). That was because all invocations are made through a special EJB reference(proxy) provided by the container. This allows the container to provide all the additional bean services such as pooling, container-managed transactions etc. So, a client can not explicitly instantiate an EJB with new operator. The client view is provided via certain interfaces that the client would have access to. The proxy realization at server side is done based on these interfaces. Different client views are defined to suite different deployment scenarios as mentioned above.

More Related Contents:

  1. What exactly is Java EE?
  2. Inject an EJB into JAX-RS (RESTful service)
  3. Should I use @EJB or @Inject
  4. EJB 3.1 @LocalBean vs no annotation
  5. Stateless and Stateful Enterprise Java Beans
  6. Correct usage of Stateful Beans with Servlets
  7. JEE7: Do EJB and CDI beans support container-managed transactions?
  8. how to create a remote session EJB from a client
  9. LOAD and CACHE application-scoped data with @Singleton and @Stateless
  10. EJB’s – when to use Remote and/or local interfaces?
  11. Why use @PostConstruct?
  12. Can I connect to SQL Server using Windows Authentication from Java EE webapp?
  13. How to create and handle composite primary key in JPA
  14. The meaning of NoInitialContextException error
  15. How to force browser to download file?
  16. Understanding JSF as a MVC framework
  17. How do I use the Jersey JSON POJO support?
  18. CDI: beans.xml, where do I put you?
  19. Finding your application’s URL with only a ServletContext
  20. How are Threads allocated to handle Servlet request?
  21. Embedded tomcat 7 servlet 3.0 annotations not working
  22. Use Enum type as a value parameter for @RolesAllowed-Annotation
  23. Mapping array with Hibernate
  24. Is there a way to run a method/class only on Tomcat/Wildfly/Glassfish startup?
  25. Thymeleaf – How to loop a list by index
  26. Besides EAR and EJB, what do I get from a Java EE app server that I don’t get in a servlet container like Tomcat?
  27. Java 11 package javax.xml.soap does not exist [duplicate]
  28. ejb lookup failing with NamingException
  29. What’s the difference between the IN and MEMBER OF JPQL operators?
  30. Root URl of the servlet

Leave a Comment