Enterprise JavaBeans will most often be deployed in conjunction with one or more Java Enterprise APIs including Java Servlets, Java Server Pages (JSP), Java Messaging Service (JMS), and Java Naming and Directory (JNDI). These APIs are briefly described below.
The Java Servlet API defines a consistent mechanism for extending the functionality of a web server with Java application code. The easiest way to describe Java Servlets is as applets that run on a web server, without a user interface. Several popular web servers, including servers from Netscape and Sun now implement the Java servlet API.
JavaServer Pages defines a facility for server-side scripting. By allowing access to server-side components from web pages, JSP separates the presentation of dynamic content from the generation of that content. Several popular web servers, including servers from Netscape and Sun, now implement JavaServer Pages.
The Java Messaging Service provides a flexible and reliable messaging service implemented in Java. With JMS, developers can implement multiple messaging schemes requiring:
publish and subscribe metaphors
The Java Naming and Directory API provides Java applications with a unified directory interface allowing access to multiple naming and directory services, including:
file system naming
By using the JNDI interface, Java developers do not tie their applications to any single directory service. Instead, JNDI-enabled applications are portable, with seamless connectivity to a wide variety of heterogeneous enterprise naming and directory services.