A session Bean is accessed from the following three clients:

• Remote client
  A remote client invokes a business method by using the remote business interface (or the remote home interface). This client invokes a method provided in the remote client view of a Session Bean.
  
• Local client
  A local client invokes a business method by using the local interface. This client invokes a method provided in the local client view of a Session Bean.
  
• Web service client
  A Web service client invokes a business method by using the Web service. This client invokes a method provided in the WebService client view of a Session Bean.
  

The No-Interface view is one of the local client views. It is available in EJB 3.1 or later.

If you use the No-Interface view, definition of a local business interface is not required. If none of the remote client view, local client view or Web service client view is implemented in an application, the No-Interface view is created by the EJB container. Even if any of the views is implemented in an application, you can use the No-Interface view by explicitly specifying the @LocalBean annotation. You need not implement any special interface for using the No-Interface view in a Session Bean.

By using the No-Interface view, you can use all the public methods in a Session Bean from the client. You can acquire the reference from a client to the No-Interface view with the DI or JNDI look-up.

No-Interface view is created when an application starts and it is available until the application stops.

Note

When you invoke a method published in the No-Interface view by the client, you cannot invoke a method that specifies an access modifier other than a public access modifier. If you invoke a method that specifies an access modifier other than a public access modifier, javax.ejb.EJBException occurs.