application server
A integrated set of Java EE software that provides several functions including a Web Server, JSP Server, JNDI Server, and an EJB Server.
application assembly
The process of collecting the various parts of a Java EE application (Web pages, JSPs, EJBs, and so on.) and placing them into WAR and EAR files for deployment onto an applications server. The resulting collection of files can also be known as being an "application assembly."
application deployment
The process of distributing the various parts of Java EE application (Web pages, JSPs, EJBs, and so on.) to the appropriate server within an application server. Application deployment is a process performed by the application server.
byte code
The Java compiler generates byte codes. A byte code is a high-level, machine-independent code for a hypothetical machine that is implemented by the Java interpreter and run-time system.
class
A software construct that defines the data (state) and methods (behavior) of the specific objects that are subsequently constructed from that class. A class in and of itself is not an object. A class is a description of an object. A class describes how the object looks and behaves when the object is created or instantiated from the specification declared by the class.
class loader
An object that is responsible for loading classes. Given the name of a class, a class loader should attempt to locate or generate data that constitutes a definition for the class. A typical strategy is to transform the name into a file name and then read a "class file" of that name from a file system.
data source
An alternative to the Driver Manager facility, a Data Source object is the preferred means of getting a connection to a particular DBMS or some other data source, such as a file. Data Source objects can provide connection pooling and distributed transactions.
deployment
See application Deployment.
deployment descriptor
An XML file within a WAR, EJB-JAR, or EAR file that contains the description of how the contents of the parts of the associated Java EE application are to be deployed by the application server.
EAR—see Enterprise Archive
EJB—see Enterprise Java Bean
EJB-JAR File
A specialized JAR file that contains the portion of the application that will be deployed to an EJB server. The EJB-JAR file includes a deployment descriptor, plus all the files needed to implement the EJB(s).
Enterprise Archive (EAR)
A specialized type of JAR file that usually contains the entire Java EE application. An EAR includes a deployment descriptor, as well as a WAR and EJB-JAR. The deployment descriptor describes the WAR and EJB-EAR files, plus any security and database information specific to the application.
Enterprise Java Bean (EJB)
A component architecture that is described as part of the Java EE specifications. EJB is used for the development and deployment of object-oriented, distributed, enterprise-level applications. Applications written using the EJB architecture are scalable, transactional, and secure.
Extensible Markup Language (XML)
A tag oriented, self-defining, markup language that defines the set of rules for describing the content and context of data within a document. Unlike other markup languages, XML is easily extended letting the markup language itself be user defined. XML describes a document's structure. It does not describe the rules of how the document should be formatted, presented or rendered. XML is a meta-markup language used for describing other markup languages.
home interface
One of two interfaces for an enterprise bean. The home interface defines zero or more methods for managing an enterprise bean. The home interface of a session bean defines create and remove methods, whereas the home interface of an entity bean defines create, finder, and remove methods.
JAR—see Java Archive
Java Archive (JAR)
A single compressed file that usually contains many different files. The types of files included in a JAR can be different. JAR files are compressed to save disk space and network bandwidth when they are transmitted across a network.
Java Remote Method Invocation (Java RMI)
A "remote procedure call (RPC)" mechanism that is native to Java. Java RMI provides a client application with the ability to invoke an EJB server application. Java RMI serializes the import and export view objects of the target EJB. These serialized objects serve as the input and output data of the invoked EJB.
Java RMI—see Java Remote Method Invocation
Java Naming and Directory Interface (JNDI)
A Java EE API that provides naming and directory functionality.
Java Server Page (JSP)
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.
Java Transaction API (JTA)
A Java EE API that lets applications and Java EE servers access transactions.
Java Platform, Enterprise Edition (Java EE)
An environment for developing and deploying enterprise applications. The Java EE platform consists of a set of services, application-programming interfaces (APIs), and protocols that provide the functionality for developing transaction oriented, multi-tiered, Web-based applications.
JNDI—see Java Naming and Directory Interface
JSP—see Java Server Page
JTA—see Java Transaction API
JVM—see Java Virtual Machine
Java EE—see Java Platform, Enterprise Edition (Java EE)
remote interface
One of two interfaces for an enterprise bean. The remote interface defines the business methods callable by a client.
servlet
A Java program that extends the functionality of a Web server, generating dynamic content, and interacting with Web clients using a request-response paradigm.
serialization
The process of saving an object's state to a sequence of bytes, as well as the process of rebuilding those bytes into a live object at some future time. The Java Serialization API provides a standard mechanism for developers to handle object serialization.
WAR—see Web Archive
Web Archive (WAR)
A specialized JAR file that contains the portion of the application that will be deployed to a Web Server. The WAR includes a deployment descriptor, plus all the files to be placed onto the Web Server.
XML—see Extensible Markup Language
|
Copyright © 2014 CA.
All rights reserved.
|
|