Sun Java Enterprise System Glossary


J2EETM application

(n.) Any deployable unit of J2EE platform functionality. This can be a single J2EE module or a group of modules packaged into an EAR file along with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers.

J2EE component

(n.) A self-contained functional software unit supported by a container and configurable at deployment time. A web application, session bean, entity bean, message-driven bean, application client, or connector. These J2EE components are written in the JavaTM programming language and are compiled in the same way as any program in the language. See also component.

J2EE module

(n.) A software unit that consists of one or more J2EE components of the same container type and one deployment descriptor of that type. Modules can be deployed as stand-alone units or can be assembled into a J2EE application. See also life-cycle module, module.

J2EE platform

(Java 2 Platform, Enterprise Edition) (n.) An environment for developing and deploying multi-tiered, web-based enterprise applications. The J2EE platform consists of a set of services, APIs, and protocols that provide the functionality for developing these applications.

J2EE product

(n.) An implementation that conforms to the J2EE platform specification.

J2EE product provider

(n.) A vendor that supplies a J2EE product.

J2EE server

(n.) The runtime portion of a J2EE product. A J2EE server provides EJB or web containers or both. See also container.

J2METM platform

(Java 2 Platform, Micro Edition) (n.) A highly optimized Java runtime environment targeting a wide range of consumer products, including pagers, cellular phones, screen phones, digital set-top boxes, and car navigation systems.

J2SETM platform

(Java 2 Platform, Standard Edition) (n.) The core Java technology platform.


(JavaBeansTM Activation Framework) (n.) Integrates support for MIME data types into the Java platform. See also MIME data type.

JAR file contract

(n.) A Java Archive file contract that specifies what information must be in the enterprise bean package.


(n.) A library for converting between code written in the Java programming language and XML. Also known as Sun Java System Web Application Framework, or Application Framework. JATO is geared toward enterprise web application development. JATO combines concepts such as display fields, application events, component hierarchies, and a page-centric development approach.

Java 2 Platform, Enterprise Edition

See J2EE platform.

Java 2 Platform, Micro Edition

See J2METM platform.

Java 2 Platform, Standard Edition

See J2SETM platform.

JavaBeanTM namespace

(n.) A standard that allows you to specify a unique label to the set of element names defined by a package. A document using that package can be included in any other document without having a conflict between element names. The elements defined in the package are uniquely identified so that, for example, the parser can determine when an element should be interpreted according to your package and not according to that of another package.

JavaBeans Activation Framework

See JAF.

JavaBeans component

(n.) A Java class that can be manipulated by tools and composed into applications. A JavaBeans component must adhere to certain property and event interface conventions.

JavaBeans component architecture

(n.) A portable, platform-independent reusable component model.

Java Enterprise System

(n.) An integration of individual Sun software products into a software system that supports distributed enterprise applications.

Java ES

See Java Enterprise System.

Java ES shared component

See shared component.

JavaMailTM (API, extension)

(n.) An API for sending and receiving email. Application code uses the Java Naming and Directory InterfaceTM (JNDI) service to locate JavaMail session resource objects using a JNDI name.

JavaScriptTM programming language

(n.) A compact, object-based scripting language for developing client and server Internet applications.

JavaServer FacesTM conversion model

(n.) A mechanism for converting between string-based markup generated by JavaServer Faces UI components and server-side Java objects.

JavaServer Faces event and listener model

(n.) A mechanism for determining how events emitted by JavaServer Faces UI components are handled. This model is based on the JavaBeans component event and listener model.

JavaServer Faces expression language

(n.) A simple expression language used by a JavaServer Faces UI component tag attributes to bind the associated component to a bean property or to bind the associated component's value to a method or an external data source, such as a bean property. Unlike JSP expression language expressions, JavaServer Faces EL expressions are evaluated by the JavaServer Faces implementation rather than by the web container.

JavaServer Faces navigation model

(n.) A mechanism for defining the sequence in which pages in a JavaServer Faces application are displayed.

JavaServer Faces UI component

(n.) A user interface control that outputs data to a client or allows a user to input data to a JavaServer Faces application.

JavaServer Faces UI component class

(n.) A JavaServer Faces class that defines the behavior and properties of a JavaServer Faces UI component.

JavaServer Faces technology

(n.) A framework for building server-side user interfaces for web applications written in the Java programming language.

JavaServer Faces validation model

(n.) A mechanism for validating the data a user inputs to a JavaServer Faces UI component.

JavaServer PagesTM technology

See JSP technology.

Java Web Start software

(n.) A web application launcher. With Java Web Start software, applications are launched by clicking on the web link. If the application is not present on the computer, Java Web Start automatically downloads the application and caches it on the computer. Once an application is downloaded to its cache, it can be launched from a desktop icon or from a browser link. No matter which method is used to launch the application, the most current version of the application is always presented.


(Java API for XML Messaging) (n.) A Java API that uses the SOAP standard to enable applications to send and receive document-oriented XML messages. These messages can be with or without attachments.


(Java API for XML Processing) (n.) An API for processing XML documents. JAXP leverages the parser standards SAX and DOM so that you can choose to parse your data as a stream of events or to build a tree-structured representation of it. JAXP supports the XSLT standard, giving you control over the presentation of the data and enabling you to convert the data to other XML documents or to other formats, such as HTML. JAXP provides namespace support, allowing you to work with schema that might otherwise have naming conflicts.


(Java API for XML Registries) (n.) A uniform and standard Java API for accessing different kinds of XML registries. Enables users to build, deploy, and discover web services. See also registry.

JAXR client

(n.) A client program that uses the JAXR API to access a business registry through a JAXR provider.

JAXR provider

(n.) An implementation of the JAXR API that provides access to a specific registry provider or to a class of registry providers that are based on a common specification.


(Java API for XML-based RPC) (n.) A Java API that enables developers to build interoperable web applications and web services based on XML-based RPC protocols.

JDBCTM connection pool

(n.) A pool that combines the JDBC data source properties used to specify a connection to a database with the connection pool properties.

JDBC resource

(n.) A resource used to connect an application running within the application server to a database by way of an existing JDBC connection pool. Consists of a Java Naming and Directory InterfaceTM (JNDI) name (which is used by the application) and the name of an existing JDBC connection pool.

JDBC technology

(Java DataBase Connectivity software) (n.) A standards-based set of classes and interfaces that enable developers to create data-aware components. The JDBC API implements methods for connecting to and interacting with data sources in a platform-independent and vendor-independent way. JDBC technology provides a call-level API for SQL-based database access.


(J-Sky hypertext markup language) Vodafone’s proprietary language used to program Japanese J-Sky devices.


(Java Message Service) (n.) A standard set of interfaces and semantics that define how a Java client accesses the facilities of a message service. These interfaces provide a standard way for programs written in the Java programming language to create, send, receive, and read messages.

JMSadministered object

(Java Message Service administered object) (n.) A pre-configured Java Message Service object (JMS connection factory or JMS destination) created by an administrator for use by one or more JMS clients. The use of administered objects allows JMS clients to be isolated from the proprietary aspects of a provider, thereby making the clients provider-independent. These objects are placed in a Java Naming and Directory InterfaceTM (JNDI) name space by an administrator and are accessed by JMS clients using JNDI lookups.


(Java Message Service API) (n.) A standard set of interfaces and semantics that define how a JMS client accesses the facilities of a JMS message service. These interfaces provide a standard way for programs written in the Java programming language to create, send, receive, and read messages.

JMS application

(Java Message Service application) (n.) One or more JMS clients that exchange messages.

JMS client

(Java Message Service client) (n.) An application or software component that interacts with other JMS clients using a JMS message service to exchange messages.

JMS connection factory

(Java Message Service connection factory) (n.) The object administered by the Java Message Service that a JMS client uses to create a connection to a JMS message service.

JMS destination

(Java Message Service destination) (n.) The physical destination in a JMS message service to which produced messages are delivered for routing and for subsequent delivery to consumers. This physical destination is identified and encapsulated by an JMS-administered object that a JMS client uses to specify the destination of incoming and outgoing messages.

JMS messages

(Java Message Service messages) (n.) Asynchronous requests, reports, or events that are consumed by Java Message Service clients. A message has a header (to which additional fields can be added) and a body. The message header specifies standard fields and optional properties. The message body contains the data that is being transmitted.

JMS provider

(Java Message Service provider) (n.) A product that implements the JMS interfaces for a messaging system and adds the administrative and control functions needed for a complete product.

JMS service

(Java Message Service service) (n.) Software that provides delivery services for a Java Message Service messaging system, including connections to JMS clients, message routing and delivery, persistence, security, and logging. The message service maintains physical destinations to which JMS clients send messages and from which the messages are delivered to consuming clients.

JMS session

(Java Message Service session) (n.) A single-threaded context for sending and receiving JMS messages. A JMS session can be non-transactional, locally transacted, or participating in a distributed transaction.

JNDI extension

(Java Naming and Directory Interface extension) (n.) A standard extension to the Java platform that provides Java technology-enabled applications with a unified interface to multiple naming and directory services in the enterprise. As part of the Java Enterprise API set, JNDI enables connectivity to heterogeneous enterprise naming and directory services.

JNDI name

(Java Naming and Directory Interface name) (n.) A name used to access a resource that has been registered in the JNDI naming service.

job controller

(n.) The MTA component responsible for scheduling and executing tasks upon request by various other MTA components.

join rule

(n.) A rule which specifies how entries in a Directory Proxy Server secondary data view are linked to entries in a primary data view, or how entries in one SQL table are linked to entries in another SQL table.

jspc utility

(n.) The compiler for pages created with JSP technology. The utility checks all JSP pages for compliance with the JSP specification.

JSPTM action

(n.) A JSP element that can act on implicit objects and other server-side objects or can define new scripting variables. Actions follow the XML syntax for elements, with a start tag, a body, and an end tag; if the body is empty it can also use the empty tag syntax. The tag must use a prefix. There are standard and custom actions.

JSP container

(n.) A container that provides the same services as a servlet container and an engine that interprets and processes JSP pages into a servlet.

JSP container, distributed

(n.) A JSP container that can run a Web application that is tagged as distributable and is spread across multiple Java virtual machines that might be running on different hosts.

JSP custom action

(n.) A user-defined action described in a portable manner by a tag library descriptor and imported into a JSP page by a taglib directive. Custom actions are used to encapsulate recurring tasks in writing JSP pages.

JSP custom tag

(n.) A tag that references a JSP custom action.

JSP declaration

(n.) A JSP scripting element that declares methods, variables, or both in a JSP page.

JSP directive

(n.) A JSP element that gives an instruction to the JSP container and is interpreted at translation time.

JSP document

(n.) A JSP page written in XML syntax and subject to the constraints of XML documents.

JSP element

(n.) A portion of a JSP page that is recognized by a JSP translator. An element can be a directive, an action, or a scripting element.

JSP expression

(n.) A scripting element that contains a valid scripting language expression that is evaluated, converted to a String, and placed into the implicit out object.

JSP expression language

(n.) A language used to write expressions that access the properties of JavaBeans components. EL expressions can be used in static text and in any standard or custom tag attribute that can accept an expression.

JSP page

(n.) A text-based document containing static text and JSP elements that describes how to process a request to create a response. A JSP page is translated into and handles requests as a servlet.

JSP scripting element

(n.) A JSP declaration, scriptlet, or expression whose syntax is defined by the JSP specification and whose content is written according to the scripting language used in the JSP page. The JSP specification describes the syntax and semantics for the case where the language page attribute is "java".

JSP scriplet

(n.) A JSP scripting element containing any code fragment that is valid in the scripting language used in the JSP page. The JSP specification describes what is a valid scriptlet for the case where the language page attribute is "java".

JSP standard action

(n.) An action that is defined in the JSP specification and is always available to a JSP page.

JSP tag file

(n.) A source file containing a reusable fragment of JSP code that is translated into a tag handler when a JSP page is translated into a servlet.

JSP tag handler

(n.) A Java programming language object that implements the behavior of a custom tag.

JSP tag library

(n.) A collection of custom tags described using a tag library descriptor and Java classes. See also JSTL.

JSP technology

(1) (n.) An extensible web technology that uses static data, JSP elements, and server-side Java objects to generate dynamic content for a client. Typically the static data is HTML or XML elements, and in many cases the client is a Web browser. Pages created with JSP technology combine the layout capabilities of a standard browser page with the power of a programming language.

(2) (n.) Extensions that enable all JSP technology metafunctions, including instantiation, initialization, destruction, access from other components, and configuration management. Reusable Java applications that run on a web server rather than in a web browser.


See Network Security Services for Java (JSS).


(Java Secure Socket Extension) (n.) A set of packages that enable secure Internet communications.


(JavaServer Pages Standard Tag Library) (n.) A tag library that encapsulates core functionality common to many JSP applications. JSTL has support for common, structural tasks such as iteration and conditionals, tags for manipulating XML documents, internationalization and locale-specific formatting tags, SQL tags, and functions.


(Java transaction API) (n.) An API that allows applications and J2EE servers to access transactions.


(Java transaction service) (n.) Specifies the implementation of a transaction manager that supports JTA and implements the Java mapping of the Object Management Group Object Transaction Service 1.1 specification at the level below the API.