A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- basic authentication
- An authentication mechanism in which a web server authenticates an entity with a user name and password obtained using the web client's built-in authentication mechanism.
- bean-managed persistence
- Data transfer between an entity bean's variables and a resource manager managed by the entity bean.
- bean-managed transaction
- A transaction whose boundaries are defined by an enterprise bean.
- business logic
- The code that implements the functionality of an application. In the Enterprise JavaBeans model, this logic is implemented by the methods of an enterprise bean.
- business method
- A method of an enterprise bean that implements the business logic or rules of an application.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- callback methods
- Component methods called by the container to notify the component of important events in its life cycle.
- caller
- Same as caller principal.
- caller principal
- The principal that identifies the invoker of the enterprise bean method.
- client certificate authentication
- An authentication mechanism in which a client uses a X.509 certificate to establish its identity.
- commit
- The point in a transaction when all updates to any resources involved in the transaction are made permanent.
- component
- An application-level software unit supported by a container. Components are configurable at deployment time. The J2EE platform defines four types of components: enterprise beans, web components, applets, and application clients.
- component contract
- The contract between a component and its container. The contract includes: life cycle management of the component, a context interface that the instance uses to obtain various information and services from its container, and a list of services that every container must provide for its components.
- connection
- See resource manager connection.
- connection factory
- See resource manager connection factory.
- connector
- A standard extension mechanism for containers to provide connectivity to enterprise information systems. A connector is specific to an enterprise information system and consists of a resource adapter and application development tools for enterprise information system connectivity. The resource adapter is plugged in to a container through its support for system-level contracts defined in the connector architecture.
- Connector architecture
- An architecture for integration of J2EE products with enterprise information systems. There are two parts to this architecture: a resource adapter provided by an enterprise information system vendor and the J2EE product that allows this resource adapter to plug in. This architecture defines a set of contracts that a resource adapter has to support to plug in to a J2EE product, for example, transactions, security, and resource management.
- container
- An entity that provides life cycle management, security, deployment, and runtime services to components. Each type of container (EJB, web, JSP, servlet, applet, and application client) also provides component-specific services.
- container-managed persistence
- Data transfer between an entity bean's variables and a resource manager managed by the entity bean's container.
- container-managed transaction
- A transaction whose boundaries are defined by an EJB container. An entity bean must use container-managed transactions.
- context attribute
- An object bound into the context associated with a servlet.
- conversational state
- The field values of a session bean plus the transitive closure of the objects reachable from the bean's fields. The transitive closure of a bean is defined in terms of the serialization protocol for the Java programming language, that is, the fields that would be stored by serializing the bean instance.
- CORBA
- Common Object Request Broker Architecture. A language independent, distributed object model specified by the Object Management Group.
- create method
- A method defined in the home interface and invoked by a client to create an enterprise bean.
- credentials
- The information describing the security attributes of a principal.
- CSS
- Cascading Style Sheet. A stylesheet used with HTML and XML documents to add a style to all elements marked with a particular tag, for the direction of browsers or other presentation mechanisms.
- CTS
- Compatibility Test Suite. A suite of compatibility tests for verifying that a J2EE product complies with the J2EE platform specification.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- delegation
- An act whereby one principal authorizes another principal to use its identity or privileges with some restrictions.
- Deployer
- A person who installs modules and J2EE applications into an operational environment.
- deployment
- The process whereby software is installed into an operational environment.
- deployment descriptor
- An XML file provided with each module and application that describes how they should be deployed. The deployment descriptor directs a deployment tool to deploy a module or application with specific container options and describes specific configuration requirements that a Deployer must resolve.
- destination
- A JMS administered object that encapsulates the identity of a JMS queue or topic. See point-to-point messaging system, publish/subscribe messaging system.
- digest authentication
- An authentication mechanism in which a web client authenticates to a web server by sending the server a message digest along its HTTP request message. The digest is computed by employing a one-way hash algorithm to a concatenation of the HTTP request message and the client's password. The digest is typically much smaller than the HTTP request, and doesn't contain the password.
- distributed application
- An application made up of distinct components running in separate runtime environments, usually on different platforms connected via a network. Typical distributed applications are two-tier (client-server), three-tier (client-middleware-server), and multitier (client-multiple middleware-multiple servers).
- DOM
- Document Object Model. A tree of objects with interfaces for traversing the tree and writing an XML version of it, as defined by the W3C specification.
- DTD
- Document Type Definition. A description of the structure and properties of a class of XML files.
- durable subscription
- In a JMS publish/subscribe messaging system, a subscription that continues to exist whether or not there is a current active subscriber object. If there is no active subscriber, JMS retains the subscription's messages until they are received by the subscription or until they expire.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- EAR file
- A JAR archive that contains a J2EE application.
- EJBTM
- See Enterprise JavaBeans.
- EJB container
- A container that implements the EJB component contract of the J2EE architecture. This contract specifies a runtime environment for enterprise beans that includes security, concurrency, life cycle management, transaction, deployment, naming, and other services. An EJB container is provided by an EJB or J2EE server.
- EJB Container Provider
- A vendor that supplies an EJB container.
- EJB context
- An object that allows an enterprise bean to invoke services provided by the container and to obtain the information about the caller of a client-invoked method.
- EJB home object
- An object that provides the life cycle operations (create, remove, find) for an enterprise bean. The class for the EJB home object is generated by the container's deployment tools. The EJB home object implements the enterprise bean's home interface. The client references an EJB home object to perform life cycle operations on an EJB object. The client uses JNDI to locate an EJB home object.
- EJB JAR file
- A JAR archive that contains an EJB module.
- EJB module
- A software unit that consists of one or more enterprise beans and an EJB deployment descriptor.
- EJB object
- An object whose class implements the enterprise bean's remote interface. A client never references an enterprise bean instance directly; a client always references an EJB object. The class of an EJB object is generated by a container's deployment tools.
- EJB server
- Software provides services to an EJB container. For example, an EJB container typically relies on a transaction manager that is part of the EJB server to perform the two-phase commit across all the participating resource managers. The J2EE architecture assumes that an EJB container is hosted by an EJB server from the same vendor, so does not specify the contract between these two entities. An EJB server may host one or more EJB containers.
- EJB Server Provider
- A vendor that supplies an EJB server.
- enterprise bean
- A component that implements a business task or business entity and resides in an EJB container; either an entity bean, session bean, or message-driven bean.
- enterprise information system
- The applications that comprise an enterprise's existing system for handling company-wide information. These applications provide an information infrastructure for an enterprise. An enterprise information system offers a well defined set of services to its clients. These services are exposed to clients as local and/or remote interfaces. Examples of enterprise information systems include: enterprise resource planning systems, mainframe transaction processing systems, and legacy database systems.
- enterprise information system resource
- An entity that provides enterprise information system-specific functionality to its clients. Examples are: a record or set of records in a database system, a business object in an enterprise resource planning system, and a transaction program in a transaction processing system.
- Enterprise Bean Provider
- An application programmer who produces enterprise bean classes, remote and home interfaces, and deployment descriptor files, and packages them in an EJB JAR file.
- Enterprise JavaBeansTM (EJBTM)
- A component architecture for the development and deployment of object-oriented, distributed, enterprise-level applications. Applications written using the Enterprise JavaBeans architecture are scalable, transactional, and secure.
- entity bean
- An enterprise bean that represents persistent data maintained in a database. An entity bean can manage its own persistence or it can delegate this function to its container. An entity bean is identified by a primary key. If the container in which an entity bean is hosted crashes, the entity bean, its primary key, and any remote references survive the crash.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- filter
- An object that can transform the header and/or content of a request or response. Filters differ from web components in that they usually do not themselves create responses but rather they modify or adapt the requests for a resource, and modify or adapt responses from a resource. A filter should not have any dependencies on a web resource for which it is acting as a filter so that it can be composable with more than one type of web resource.
- finder method
- A method defined in the home interface and invoked by a client to locate an entity bean.
- form-based authentication
- An authentication mechanism in which a web container provides an application-specific form for logging in.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- handle
- An object that identifies an enterprise bean. A client may serialize the handle, and then later deserialize it to obtain a reference to the enterprise bean.
- 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, while the home interface of an entity bean defines create, finder, and remove methods.
- home handle
- An object that can be used to obtain a reference of the home interface. A home handle can be serialized and written to stable storage and deserialized to obtain the reference.
- HTML
- Hypertext Markup Language. A markup language for hypertext documents on the Internet. HTML enables the embedding of images, sounds, video streams, form fields, references to other objects with URLs and basic text formatting.
- HTTP
- Hypertext Transfer Protocol. The Internet protocol used to fetch hypertext objects from remote hosts. HTTP messages consist of requests from client to server and responses from server to client.
- HTTPS
- HTTP layered over the SSL protocol.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- impersonation
- An act whereby one entity assumes the identity and privileges of another entity without restrictions and without any indication visible to the recipients of the impersonator's calls that delegation has taken place. Impersonation is a case of simple delegation.
- IDL
- Interface Definition Language. A language used to define interfaces to remote CORBA objects. The interfaces are independent of operating systems and programming languages.
- IIOP
- Internet Inter-ORB Protocol. A protocol used for communication between CORBA object request brokers.
- initialization parameter
- A parameter that initializes the context associated with a servlet.
- ISV
- Independent Software Vendor.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- J2EETM
- See Java 2 Platform, Enterprise Edition.
- J2METM
- See Java 2 Platform, Micro Edition.
- J2SETM
- See Java 2 Platform, Standard Edition.
- J2EE application
- Any deployable unit of J2EE functionality. This can be a single module or a group of modules packaged into an .ear file with a J2EE application deployment descriptor. J2EE applications are typically engineered to be distributed across multiple computing tiers.
- J2EE product
- An implementation that conforms to the J2EE platform specification.
- J2EE Product Provider
- A vendor that supplies a J2EE product.
- J2EE server
- The runtime portion of a J2EE product. A J2EE server provides EJB and/or web containers.
- JAR Java ARchive
- A platform-independent file format that permits many files to be aggregated into one file.
- JavaTM 2 Platform, Enterprise Edition (J2EE)
- An environment for developing and deploying enterprise applications. The J2EE platform consists of a set of services, application programming interfaces (APIs), and protocols that provide the functionality for developing multitiered, web-based applications.
- JavaTM 2 Platform, Micro Edition (J2SE)
- A highly optimized Java runtime environment targeting a wide range of consumer products, including pagers, cellular phones, screenphones, digital set-top boxes and car navigation systems.
- JavaTM 2 Platform, Standard Edition (J2SE)
- The core Java technology platform.
- JavaTM 2 SDK, Enterprise Edition (J2EE SDK)
- Sun's implementation of the J2EE platform. This implementation provides an operational definition of the J2EE platform.
- JavaTM Message Service (JMS)
- An API for using enterprise messaging systems such as IBM MQ Series, TIBCO Rendezvous, and so on.
- Java Naming and Directory InterfaceTM (JNDI)
- An API that provides naming and directory functionality.
- JavaTM Transaction API (JTA)
- An API that allows applications and J2EE servers to access transactions.
- JavaTM Transaction Service (JTS)
- Specifies the implementation of a transaction manager which supports JTA and implements the Java mapping of the OMG Object Transaction Service (OTS) 1.1 specification at the level below the API.
- JavaBeansTM component
- A Java class that can be manipulated in a visual builder tool and composed into applications. A JavaBeans component must adhere to certain property and event interface conventions.
- Java IDL
- A technology that provides CORBA interoperability and connectivity capabilities for the J2EE platform. These capabilities enable J2EE applications to invoke operations on remote network services using the OMG IDL and IIOP.
- JavaMailTM
- An API for sending and receiving email.
- JavaServer PagesTM (JSPTM)
- An extensible web technology that uses template data, custom elements, scripting languages, and server-side Java objects to return dynamic content to a client. Typically the template data is HTML or XML elements, and in many cases the client is a web browser.
- JDBCTM
- An API for database-independent connectivity between the J2EE platform and a wide range of data sources.
- JMS
- See Java Message Service.
- JMS administered object
- A preconfigured JMS object (a resource manager connection factory or a destination) created by an administrator for the use of JMS clients and placed in a JNDI namespace.
- JMS application
- One or more JMS clients that exchange messages.
- JMS client
- A Java language program that sends and/or receives messages.
- JMS provider
- A messaging system that implements the Java Message Service as well as other administrative and control functionality needed in a full-featured messaging product.
- JMS session
- A single-threaded context for sending and receiving JMS messages. A JMS session can be non-transacted, locally transacted, or participating in a distributed transaction.
- JNDI
- See Java Naming and Directory Interface.
- JSP
- See JavaServer Pages.
- JSP action
- 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.
- JSP action, custom
- An action described in a portable manner by a tag library descriptor and a collection of Java classes and imported into a JSP page by a
taglibdirective. A custom action is invoked when a JSP page uses a custom tag.
- JSP action, standard
- An action that is defined in the JSP specification and is always available to a JSP file without being imported.
- JSP application
- A stand-alone web application, written using the JavaServer Pages technology, that can contain JSP pages, servlets, HTML files, images, applets, and JavaBeans components.
- JSP container
- 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
- 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 declaration
- A JSP scripting element that declares methods, variables, or both in a JSP file.
- JSP directive
- A JSP element that gives an instruction to the JSP container and is interpreted at translation time.
- JSP element
- 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
- A scripting element that contains a valid scripting language expression that is evaluated, converted to a
String, and placed into the implicitoutobject.
- JSP file
- A file that contains a JSP page. In the Servlet 2.2 specification, a JSP file must have a .jsp extension.
- JSP page
- A text-based document using fixed template data and JSP elements that describes how to process a request to create a response.
- JSP scripting element
- A JSP declaration, scriptlet, or expression, whose tag 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 scriptlet
- 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 tag
- A piece of text between a left angle bracket and a right angle bracket that is used in a JSP file as part of a JSP element. The tag is distinguishable as markup, as opposed to data, because it is surrounded by angle brackets.
- JSP tag library
- A collection of custom tags identifying custom actions described via a tag library descriptor and Java classes.
- JTA
- See Java Transaction API.
- JTS
- See Java Transaction Service.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- life cycle
- The framework events of a component's existence. Each type of component has defining events which mark its transition into states where it has varying availability for use. For example, a servlet is created and has its
initmethod called by its container prior to invocation of its service method by clients or other servlets who require its functionality. After the call of itsinitmethod it has the data and readiness for its intended use. The servlet'sdestroymethod is called by its container prior to the ending of its existence so that processing associated with winding up may be done, and resources may be released. Theinitanddestroymethods in this example are callback methods. Similar considerations apply to all J2EE component types: enterprise beans (EJBs), web components (servlets or JSP pages), applets, and application clients.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- message
- In the Java Message Service, an asynchronous request, report, or event that is created, sent, and consumed by an enterprise application, not by a human. It contains vital information needed to coordinate enterprise applications, in the form of precisely formatted data that describes specific business actions.
- MessageConsumer
- An object created by a JMS session that is used for receiving messages sent to a destination.
- MessageProducer
- An object created by a JMS session that is used for sending messages to a destination.
- message-driven bean
- An enterprise bean that is an asynchronous message consumer. A message-driven bean has no state for a specific client, but its instance variables may contain state across the handling of client messages, including an open database connection and an object reference to an EJB object. A client accesses a message-driven bean by sending messages to the destination for which the message-driven bean is a message listener.
- method permission
- An authorization rule that determines who is permitted to execute one or more enterprise bean methods.
- module
- A software unit that consists of one or more J2EE components of the same container type and one deployment descriptor of that type. There are three types of modules: EJB, web, and application client. Modules can be deployed as stand-alone units or assembled into an application.
- mutual authentication
- An authentication mechanism employed by two parties for the purpose of proving each other's identity to one another.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- naming context
- A set of associations between unique, atomic, people-friendly identifiers and objects.
- naming environment
- A mechanism that allows a component to be customized without the need to access or change the component's source code. A container implements the component's naming environment, and provides it to the component as a JNDI naming context. Each component names and accesses its environment entries using the
java:comp/envJNDI context. The environment entries are declaratively specified in the component's deployment descriptor.
- non-JMS client
- A messaging client program that uses a message system's native client API instead of the Java Message Service.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- ORB
- Object Request Broker. A library than enables CORBA objects to locate and communicate with one another.
- OS principal
- A principal native to the operating system on which the J2EE platform is executing.
- OTS
- Object Transaction Service. A definition of the interfaces that permit CORBA objects to participate in transactions.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- passivation
- The process of transferring an enterprise bean from memory to secondary storage. (See activation.)
- persistence
- The protocol for transferring the state of an entity bean between its instance variables and an underlying database.
- POA
- Portable Object Adapter. A CORBA standard for building server-side applications that are portable across heterogeneous ORBs.
- point-to-point message system
- A messaging system built around the concept of message queues. Each message is addressed to a specific queue; clients extract messages from the queue(s) established to hold their messages.
- principal
- The identity assigned to an user as a result of authentication.
- privilege
- A security attribute that does not have the property of uniqueness and that may be shared by many principals.
- primary key
- An object that uniquely identifies an entity bean within a home.
- publish/subscribe message system
- A messaging system in which clients address messages to a specific node in a content hierarchy. Publishers and subscribers are generally anonymous and may dynamically publish or subscribe to the content hierarchy. The system takes care of distributing the messages arriving from a node's multiple publishers to its multiple subscribers.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- queue
- See point-to-point messaging system.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- realm
- See security policy domain. Also, a string, passed as part of an HTTP request during basic authentication, that defines a protection space. The protected resources on a server can be partitioned into a set of protection spaces, each with its own authentication scheme and/or authorization database.
- re-entrant entity bean
- An entity bean that can handle multiple simultaneous, interleaved, or nested invocations which will not interfere with each other.
- Reference Implementation
- See Java 2 SDK, Enterprise Edition.
- remote interface
- One of two interfaces for an enterprise bean. The remote interface defines the business methods callable by a client.
- remove method
- Method defined in the home interface and invoked by a client to destroy an enterprise bean.
- resource adapter
- A system-level software driver that is used by an EJB container or an application client to connect to an enterprise information system. A resource adapter is typically specific to an enterprise information system. It is available as a library and is used within the address space of the server or client using it. A resource adapter plugs in to a container. The application components deployed on the container then use the client API (exposed by adapter) or tool generated high-level abstractions to access the underlying enterprise information system. The resource adapter and EJB container collaborate to provide the underlying mechanisms-transactions, security, and connection pooling-for connectivity to the enterprise information system.
- resource manager
- Provides access to a set of shared resources. A resource manager participates in transactions that are externally controlled and coordinated by a transaction manager. A resource manager is typically in different address space or on a different machine from the clients that access it. Note: An enterprise information system is referred to as resource manager when it is mentioned in the context of resource and transaction management.
- resource manager connection
- An object that represents a session with a resource manager.
- resource manager connection factory
- An object used for creating a resource manager connection.
- RMI
- Remote Method Invocation. A technology that allows an object running in one Java virtual machine to invoke methods on an object running in a different Java virtual machine.
- RMI-IIOP
- A version of RMI implemented to use the CORBA IIOP protocol. RMI over IIOP provides interoperability with CORBA objects implemented in any language if all the remote interfaces are originally defined as RMI interfaces.
- role (development)
- The function performed by a party in the development and deployment phases of an application developed using J2EE technology. The roles are: Application Component Provider, Application Assembler, Deployer, J2EE Product Provider, EJB Container Provider, EJB Server Provider, Web Container Provider, Web Server Provider, Tool Provider, and System Administrator.
- role (security)
- An abstract logical grouping of users that is defined by the Application Assembler. When an application is deployed, the roles are mapped to security identities, such as principals or groups, in the operational environment.
- role mapping
- The process of associating the groups and/or principals recognized by the container to security roles specified in the deployment descriptor. Security roles have to be mapped by the Deployer before the component is installed in the server.
- rollback
- The point in a transaction when all updates to any resources involved in the transaction are reversed.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- SAX
- Simple API for XML. An event-driven, serial-access mechanism for accessing XML documents.
- security attributes
- A set of properties associated with a principal. Security attributes can be associated with a principal by an authentication protocol and/or by a J2EE Product Provider.
- security constraint
- A declarative way to annotate the intended protection of web content. A security constraint consists of a web resource collection, an authorization constraint, and a user data constraint.
- security context
- An object that encapsulates the shared state information regarding security between two entities.
- security permission
- A mechanism, defined by J2SE, used by the J2EE platform to express the programming restrictions imposed on Application Component Providers.
- security permission set
- The minimum set of security permissions that a J2EE Product Provider must provide for the execution of each component type.
- security policy domain
- A scope over which security policies are defined and enforced by a security administrator. A security policy domain has a collection of users (or principals), uses a well defined authentication protocol(s) for authenticating users (or principals), and may have groups to simplify setting of security policies.
- security role
- See role (security).
- security technology domain
- A scope over which the same security mechanism is used to enforce a security policy. Multiple security policy domains can exist within a single technology domain.
- security view
- The set of security roles defined by the Application Assembler.
- server principal
- The OS principal that the server is executing as.
- 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.
- servlet container
- A container that provides the network services over which requests and responses are sent, decodes requests, and formats responses. All servlet containers must support HTTP as a protocol for requests and responses, but may also support additional request-response protocols such as HTTPS.
- servlet container, distributed
- A servlet container that can run a web application that is tagged as distributable and that executes across multiple Java virtual machines running on the same host or on different hosts.
- servlet context
- An object that contains a servlet's view of the web application within which the servlet is running. Using the context, a servlet can log events, obtain URL references to resources, and set and store attributes that other servlets in the context can use.
- servlet mapping
- Defines an association between a URL pattern and a servlet. The mapping is used to map requests to servlets.
- session
- An object used by a servlet to track a user's interaction with a web application across multiple HTTP requests.
- session bean
- An enterprise bean that is created by a client and that usually exists only for the duration of a single client-server session. A session bean performs operations, such as calculations or accessing a database, for the client. While a session bean may be transactional, it is not recoverable should a system crash occur. Session bean objects can be either stateless or they can maintain conversational state across methods and transactions. If a session bean maintains state, then the EJB container manages this state if the object must be removed from memory. However, the session bean object itself must manage its own persistent data.
- SSL
- Secure Socket Layer. A security protocol that provides privacy over the Internet. The protocol allows client-server applications to communicate in a way that cannot be eavesdropped or tampered with. Servers are always authenticated and clients are optionally authenticated.
- SQL
- Structured Query Language. The standardized relational database language for defining database objects and manipulating data.
- SQL/J
- A set of standards that includes specifications for embedding SQL statements in methods in the Java programming language and specifications for calling Java static methods as SQL stored procedures and user-defined functions. An SQL checker can detects errors in static SQL statements at program development time, rather than at execution time as with a JDBC driver.
- stateful session bean
- A session bean with a conversational state.
- stateless session bean
- A session bean with no conversational state. All instances of a stateless session bean are identical.
- System Administrator
- The person responsible for configuring and administering the enterprise's computers, networks, and software systems.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- topic
- See publish-subscribe messaging system.
- transaction
- An atomic unit of work that modifies data. A transaction encloses one or more program statements, all of which either complete or roll back. Transactions enable multiple users to access the same data concurrently.
- transaction attribute
- A value specified in an enterprise bean's deployment descriptor that is used by the EJB container to control the transaction scope when the enterprise bean's methods are invoked. A transaction attribute can have the following values:
Required,RequiresNew,Supports,NotSupported,Mandatory,Never.
- transaction isolation level
- The degree to which the intermediate state of the data being modified by a transaction is visible to other concurrent transactions and data being modified by other transactions is visible to it.
- transaction manager
- Provides the services and management functions required to support transaction demarcation, transactional resource management, synchronization, and transaction context propagation.
- Tool Provider
- An organization or software vendor that provides tools used for the development, packaging, and deployment of J2EE applications.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- URI
- Uniform Resource Identifier. A compact string of characters for identifying an abstract or physical resource. A URI is either a URL or a URN. URLs and URNs are concrete entities that actually exist; A URI is an abstract superclass.
- URL
- Uniform Resource Locator. A standard for writing a textual reference to an arbitrary piece of data in the World Wide Web. A URL looks like
protocol://host/localinfowhereprotocolspecifies a protocol for fetching the object (such as HTTP or FTP),hostspecifies the Internet name of the targeted host, andlocalinfois a string (often a file name) passed to the protocol handler on the remote host.
- URL path
- The URL passed by a HTTP request to invoke a servlet. The URL consists of the Context Path + Servlet Path + Path Info, where
- Context Path is the path prefix associated with a servlet context that this servlet is a part of. If this context is the default context rooted at the base of the web server's URL namespace, the path prefix will be an empty string. Otherwise, the path prefix starts with a / character but does not end with a / character.
- Servlet Path is the path section that directly corresponds to the mapping which activated this request. This path starts with a / character.
- Path Info is the part of the request path that is not part of the Context Path or the Servlet Path.
- URN
- Uniform Resource Name. A unique identifier that identifies an entity, but doesn't tell where it is located. A system can use a URN to look up an entity locally before trying to find it on the web. It also allows the web location to change, while still allowing the entity to be found.
- user data constraint
- Indicates how data between a client and a web container should be protected. The protection can be the prevention of tampering with the data or prevention of eavesdropping on the data.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- WAR file
- A JAR archive that contains a web module.
- web application
- An application written for the Internet, including those built with Java technologies such as JavaServer Pages and servlets, as well as those built with non-Java technologies such as CGI and Perl.
- web application, distributable
- A web application that uses J2EE technology written so that it can be deployed in a web container distributed across multiple Java virtual machines running on the same host or different hosts. The deployment descriptor for such an application uses the distributable element.
- web component
- A component that provides services in response to requests; either a servlet or a JSP page.
- web container
- A container that implements the web component contract of the J2EE architecture. This contract specifies a runtime environment for web components that includes security, concurrency, life cycle management, transaction, deployment, and other services. A web container provides the same services as a JSP container and a federated view of the J2EE platform APIs. A web container is provided by a web or J2EE server.
- web container, distributed
- A web container that can run a web application that is tagged as distributable and that executes across multiple Java virtual machines running on the same host or on different hosts.
- Web Container Provider
- A vendor that supplies a web container.
- web module
- A unit that consists of one or more web components and a web deployment descriptor.
- web resource collection
- A list of URL patterns and HTTP methods that describe a set of resources to be protected.
- web server
- Software that provides services to access the Internet, an intranet, or an extranet. A web server hosts web sites, provides support for HTTP and other protocols, and executes server-side programs (such as CGI scripts or servlets) that perform certain functions. In the J2EE architecture, a web server provides services to a web container. For example, a web container typically relies on a web server to provide HTTP message handling. The J2EE architecture assumes that a web container is hosted by a web server from the same vendor, so does not specify the contract between these two entities. A web server may host one or more web containers.
- Web Server Provider
- A vendor that supplies a web server.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
- XML
- Extensible Markup Language. A markup language that allows you to define the tags (markup) needed to identify the content, data, and text, in XML documents. It differs from HTML the markup language most often used to present information on the internet. HTML has fixed tags that deal mainly with style or presentation. An XML document must undergo a transformation into a language with style tags under the control of a stylesheet before it can be presented by a browser or other presentation mechanism. Two types of style sheets used with XML are CSS and XSL. Typically, XML is transformed into HTML for presentation. Although tags may be defined as needed in the generation of an XML document, a Document Type Definition ( DTD) may be used to define the elements allowed in a particular type of document. A document may be compared with the rules in the DTD to determine its validity and to locate particular elements in the document. J2EE deployment descriptors are expressed in XML with DTDs defining allowed elements. Programs for processing XML documents use SAX or DOM APIs. J2EE deployment descriptors are expressed in XML.
- XSL
- Extensible Stylesheet Language. An XML transformation language used for transforming XML documents into documents with flow object tags for presentation purposes. The transformation aspect of XSL has been abstracted into XSLT with the XSL name now used to designate the presentation flow language. XSL is a direct descendent of the DSSSL style language for SGML (Standard Generalized Markup Language), the language from which XML was subsetted. It was designed to have all the capabilities of CSS, the stylesheet often used with HTML. XSL flow objects can be presented by specialized browsers, and themselves transformed into PDF documents.
- XSLT
- XSL Transformation. An XML file that controls the transformation of an XML document into another XML document or HTML. The target document often will have presentation related tags dictating how it will be rendered by a browser or other presentation mechanism. XSLT was formerly part of XSL, which also included a tag language of style flow objects.
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (top)
posted by colleen at
5:22 AM
