Explore topic-wise InterviewSolutions in .

CORBA is useful in many situations. Because of the easy way that CORBA INTEGRATES MACHINES from so many vendors, with sizes ranging from mainframes through minis and desktops to hand-helds and embedded systems, it is the middleware of choice for large (and even not-so-large) enterprises. One of its most important, as well most frequent, uses is in servers that must handle large number of CLIENTS, at high hit rates, with high reliability. CORBA works behind the scenes in the computer rooms of many of the world's largest websites; ones that you probably use every day. Specializations for scalability and fault-tolerance support these systems. But it's not used just for large applications; SPECIALIZED versions of CORBA run real-time systems, and small embedded systems.

CORBA is useful in many situations. Because of the easy way that CORBA integrates machines from so many vendors, with sizes ranging from mainframes through minis and desktops to hand-helds and embedded systems, it is the middleware of choice for large (and even not-so-large) enterprises. One of its most important, as well most frequent, uses is in servers that must handle large number of clients, at high hit rates, with high reliability. CORBA works behind the scenes in the computer rooms of many of the world's largest websites; ones that you probably use every day. Specializations for scalability and fault-tolerance support these systems. But it's not used just for large applications; specialized versions of CORBA run real-time systems, and small embedded systems.

Enterprise JavaBeans components CONTAINS Business CODE, which is LOGIC that solves or meets the needs of a particular business domain such as BANKING, retail, or finance, is handled by enterprise beans running in the business tier. All the business code is contained inside an Enterprise Bean which receives data from client programs, processes it (if necessary), and sends it to the enterprise information system tier for storage. An enterprise bean also RETRIEVES data from storage, processes it (if necessary), and sends it back to the client program.

Enterprise JavaBeans components contains Business code, which is logic that solves or meets the needs of a particular business domain such as banking, retail, or finance, is handled by enterprise beans running in the business tier. All the business code is contained inside an Enterprise Bean which receives data from client programs, processes it (if necessary), and sends it to the enterprise information system tier for storage. An enterprise bean also retrieves data from storage, processes it (if necessary), and sends it back to the client program.

No, It DEPENDS on type of application that client wants. A J2EE application can be web-based or non-web-based. if an application client executes on the client machine, it is a non-web-based J2EE application. The J2EE application can provide a way for users to handle tasks such as J2EE SYSTEM or application administration. It typically has a graphical user interface created from Swing or AWT APIS, or a command-line interface. When user request, it can open an HTTP connection to establish COMMUNICATION with a servlet RUNNING in the web tier.

No, It depends on type of application that client wants. A J2EE application can be web-based or non-web-based. if an application client executes on the client machine, it is a non-web-based J2EE application. The J2EE application can provide a way for users to handle tasks such as J2EE system or application administration. It typically has a graphical user interface created from Swing or AWT APIs, or a command-line interface. When user request, it can open an HTTP connection to establish communication with a servlet running in the web tier.

No. JavaBeans components are not considered J2EE components by the J2EE specification. They are written to manage the DATA flow between an application CLIENT or applet and components running on the J2EE server or between server components and a database. JavaBeans components written for the J2EE platform have instance variables and get and set methods for ACCESSING the data in the instance variables. JavaBeans components used in this way are typically SIMPLE in design and implementation, but should conform to the naming and design conventions outlined in the JavaBeans component architecture.

No. JavaBeans components are not considered J2EE components by the J2EE specification. They are written to manage the data flow between an application client or applet and components running on the J2EE server or between server components and a database. JavaBeans components written for the J2EE platform have instance variables and get and set methods for accessing the data in the instance variables. JavaBeans components used in this way are typically simple in design and implementation, but should conform to the naming and design conventions outlined in the JavaBeans component architecture.

No. STATIC HTML pages and applets are bundled with web components during application ASSEMBLY, but are not CONSIDERED web components by the J2EE specification. Even the server-side utility classes are not considered web components, EITHER.

No. Static HTML pages and applets are bundled with web components during application assembly, but are not considered web components by the J2EE specification. Even the server-side utility classes are not considered web components, either.

Containers are the interface between a component and the low-level PLATFORM specific functionality that supports the component. Before a Web, enterprise bean, or application CLIENT component can be executed, it MUST be ASSEMBLED into a J2EE application and DEPLOYED into its container.

Containers are the interface between a component and the low-level platform specific functionality that supports the component. Before a Web, enterprise bean, or application client component can be executed, it must be assembled into a J2EE application and deployed into its container.

J2EE WEB components can be either servlets or JSP pages. Servlets are Java PROGRAMMING language classes that dynamically process requests and construct RESPONSES. JSP pages are text-based documents that execute as servlets but allow a more natural approach to creating static content.

J2EE Web components can be either servlets or JSP pages. Servlets are Java programming language classes that dynamically process requests and construct responses. JSP pages are text-based documents that execute as servlets but allow a more natural approach to creating static content.

A CONTAINER is a runtime support of a system-level entity. Containers provide components with services such as LIFECYCLE management, SECURITY, deployment, and THREADING.

A container is a runtime support of a system-level entity. Containers provide components with services such as lifecycle management, security, deployment, and threading.

IManages the execution of APPLETS. Consists of a Web browser and Java PLUGIN running on the CLIENT TOGETHER.

IManages the execution of applets. Consists of a Web browser and Java Plugin running on the client together.

Servlet and JSP containers are collectively referred to as Web containers. It MANAGES the execution of JSP PAGE and servlet COMPONENTS for J2EE APPLICATIONS. Web components and their container run on the J2EE server.

Servlet and JSP containers are collectively referred to as Web containers. It manages the execution of JSP page and servlet components for J2EE applications. Web components and their container run on the J2EE server.

An EAR file is a STANDARD JAR file with an .ear extension, named from Enterprise ARCHIVE file. A J2EE APPLICATION with all of its MODULES is delivered in EAR file.

An EAR file is a standard JAR file with an .ear extension, named from Enterprise ARchive file. A J2EE application with all of its modules is delivered in EAR file.

JTA is the ABBREVIATION for the Java Transaction API. JTS is the abbreviation for the Jave Transaction Service. JTA provides a standard interface and allows you to demarcate transactions in a manner that is independent of the transaction MANAGER implementation. The J2EE SDK implements the transaction manager with JTS. But your code doesn’t call the JTS methods directly. Instead, it invokes the JTA methods, which then call the lower-level JTS routines. Therefore, JTA is a high level transaction interface that your application uses to control transaction. and JTS is a low level transaction interface and ejb uses behind the SCENES (client code doesn’t directly interact with JTS. It is based on object transaction service(OTS) which is part of CORBA.

JTA is the abbreviation for the Java Transaction API. JTS is the abbreviation for the Jave Transaction Service. JTA provides a standard interface and allows you to demarcate transactions in a manner that is independent of the transaction manager implementation. The J2EE SDK implements the transaction manager with JTS. But your code doesn’t call the JTS methods directly. Instead, it invokes the JTA methods, which then call the lower-level JTS routines. Therefore, JTA is a high level transaction interface that your application uses to control transaction. and JTS is a low level transaction interface and ejb uses behind the scenes (client code doesn’t directly interact with JTS. It is based on object transaction service(OTS) which is part of CORBA.

JAXP stands for Java API for XML. XML is a LANGUAGE for representing and describing text-based data which can be read and handled by any program or tool that uses XML APIs. It PROVIDES standard services to determine the type of an arbitrary piece of data, encapsulate ACCESS to it, discover the operations available on it, and create the appropriate JavaBeans component to perform those operations.

JAXP stands for Java API for XML. XML is a language for representing and describing text-based data which can be read and handled by any program or tool that uses XML APIs. It provides standard services to determine the type of an arbitrary piece of data, encapsulate access to it, discover the operations available on it, and create the appropriate JavaBeans component to perform those operations.

The J2EE Connector API is used by J2EE TOOLS vendors and system integrators to create resource adapters that support access to ENTERPRISE information systems that can be plugged into any J2EE product. Each TYPE of database or EIS has a different resource adapter. Note: A resource adapter is a software component that allows J2EE application components to access and interact with the underlying resource manager. Because a resource adapter is specific to its resource manager, there is TYPICALLY a different resource adapter for each type of database or enterprise information system.

The J2EE Connector API is used by J2EE tools vendors and system integrators to create resource adapters that support access to enterprise information systems that can be plugged into any J2EE product. Each type of database or EIS has a different resource adapter. Note: A resource adapter is a software component that allows J2EE application components to access and interact with the underlying resource manager. Because a resource adapter is specific to its resource manager, there is typically a different resource adapter for each type of database or enterprise information system.

The Java Authentication and Authorization Service (JAAS) provides a way for a J2EE application to authenticate and AUTHORIZE a specific USER or group of users to run it. It is a standard Pluggable Authentication Module (PAM) framework that extends the Java 2 platform SECURITY architecture to support user-based authorization.

The Java Authentication and Authorization Service (JAAS) provides a way for a J2EE application to authenticate and authorize a specific user or group of users to run it. It is a standard Pluggable Authentication Module (PAM) framework that extends the Java 2 platform security architecture to support user-based authorization.

The JNDI provides naming and directory functionality. It provides APPLICATIONS with methods for performing standard directory operations, such as associating attributes with objects and searching for objects using their attributes. Using JNDI, a J2EE application can STORE and retrieve any TYPE of named Java object. Because JNDI is independent of any specific implementations, applications can use JNDI to access multiple naming and directory services, including existing naming and directory services such as LDAP, NDS, DNS, and NIS.

The JNDI provides naming and directory functionality. It provides applications with methods for performing standard directory operations, such as associating attributes with objects and searching for objects using their attributes. Using JNDI, a J2EE application can store and retrieve any type of named Java object. Because JNDI is independent of any specific implementations, applications can use JNDI to access multiple naming and directory services, including existing naming and directory services such as LDAP, NDS, DNS, and NIS.

The J2EE platform uses a multitiered DISTRIBUTED application model. Application logic is divided into components ACCORDING to function, and the various application components that make up a J2EE application are INSTALLED on different machines depending on the tier in the multitiered J2EE environment to which the application component belongs.

The J2EE application parts are:

• Client-tier components run on the client MACHINE.
• Web-tier components run on the J2EE server.
• Business-tier components run on the J2EE server.
• ENTERPRISE information system (EIS)-tier software runs on the EIS server.

The J2EE platform uses a multitiered distributed application model. Application logic is divided into components according to function, and the various application components that make up a J2EE application are installed on different machines depending on the tier in the multitiered J2EE environment to which the application component belongs.

The J2EE application parts are:

In the Java Message Service, an asynchronous request, report, or event that is created, sent, and consumed by an ENTERPRISE application and 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.

In the Java Message Service, an asynchronous request, report, or event that is created, sent, and consumed by an enterprise application and 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.

A mechanism for DEFINING the characteristics of JAVABEANS COMPONENTS used in a JavaServer FACES application.

A mechanism for defining the characteristics of JavaBeans components used in a JavaServer Faces application.

That PART of the DTD that is defined within the current XML FILE.

That part of the DTD that is defined within the current XML file.

A set of phases during which a request for a page is received, a UI component tree REPRESENTING the page is processed, and a response is produced. During the phases of the life cycle: The local data of the components is updated with the VALUES contained in the request parameters. Events generated by the components are processed. Validators and converters registered on the components are processed. The components' local data is updated to back-end objects. The response is RENDERED to the client while the component STATE of the response is saved on the server for future requests.

A set of phases during which a request for a page is received, a UI component tree representing the page is processed, and a response is produced. During the phases of the life cycle: The local data of the components is updated with the values contained in the request parameters. Events generated by the components are processed. Validators and converters registered on the components are processed. The components' local data is updated to back-end objects. The response is rendered to the client while the component state of the response is saved on the server for future requests.

The framework events of a J2EE component's existence. Each type of component has defining events that mark its TRANSITION into states in which it has varying availability for use. For example, a servlet is created and has its init METHOD called by its CONTAINER before invocation of its service method by clients or other servlets that require its functionality. After the call of its init method, it has the data and readiness for its intended use. The servlet's destroy method is called by its container before the ending of its existence so that processing associated with winding up can be done and resources can be released. The init and destroy methods in this example are CALLBACK methods. Similar considerations apply to the life cycle of all J2EE component types: enterprise beans, Web components (servlets or JSP pages), applets, and application clients.

The framework events of a J2EE component's existence. Each type of component has defining events that mark its transition into states in which it has varying availability for use. For example, a servlet is created and has its init method called by its container before invocation of its service method by clients or other servlets that require its functionality. After the call of its init method, it has the data and readiness for its intended use. The servlet's destroy method is called by its container before the ending of its existence so that processing associated with winding up can be done and resources can be released. The init and destroy methods in this example are callback methods. Similar considerations apply to the life cycle of all J2EE component types: enterprise beans, Web components (servlets or JSP pages), applets, and application clients.

ABBREVIATE of JAVA TRANSACTION SERVICE.

Abbreviate of Java Transaction Service.

ABBREVIATE of JavaServer PAGES STANDARD TAG LIBRARY.

Abbreviate of JavaServer Pages Standard Tag Library.

A collection of CUSTOM tags DESCRIBED via a tag library DESCRIPTOR and JAVA classes.

A collection of custom tags described via a tag library descriptor and Java classes.

A JSP ELEMENT that gives an instruction to the JSP container and is interpreted at translation TIME.

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

A JSP SCRIPTING ELEMENT that DECLARES methods, VARIABLES, or both in a JSP page.

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

A TAG that REFERENCES a JSP CUSTOM ACTION.

A tag that references a JSP custom action.

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.

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.

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.

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.

A CONTAINER that provides the same services as a servlet container and an ENGINE that INTERPRETS and processes JSP pages into a servlet.

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

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.

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.

ABBREVIATE of JavaServer PAGES.

Abbreviate of JavaServer Pages.

A single-threaded context for SENDING and RECEIVING JMS MESSAGES. A JMS session can be nontransacted, locally transacted, or participating in a DISTRIBUTED transaction.

A single-threaded context for sending and receiving JMS messages. A JMS session can be nontransacted, locally transacted, or participating in a distributed transaction.

A messaging SYSTEM that implements the JAVA Message Service as well as other administrative and control FUNCTIONALITY NEEDED in a full-featured messaging PRODUCT.

A messaging system that implements the Java Message Service as well as other administrative and control functionality needed in a full-featured messaging product.

A JAVA LANGUAGE program that SENDS or RECEIVES messages.

A Java language program that sends or receives messages.

ONE or more JMS CLIENTS that EXCHANGE MESSAGES.

One or more JMS clients that exchange messages.

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.

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.

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.

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.

A CLIENT program that uses the JAXR API to access a business registry VIA a JAXR PROVIDER.

A client program that uses the JAXR API to access a business registry via a JAXR provider.

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.

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.

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.

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.

A MECHANISM for validating the DATA a USER inputs to a JavaServer FACES UI component.

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

A JavaServer FACES CLASS that DEFINES the behavior and PROPERTIES of a JavaServer Faces UI component.

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

A USER INTERFACE control that OUTPUTS data to a client or ALLOWS a user to input data to a JavaServer Faces application.

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

A mechanism for DEFINING the SEQUENCE in which PAGES in a JavaServer Faces application are displayed.

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

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 EL expressions, JavaServer Faces EL expressions are evaluated by the JavaServer Faces implementation RATHER than by the Web container.

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 EL expressions, JavaServer Faces EL expressions are evaluated by the JavaServer Faces implementation rather than by the Web container.

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.

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.

A mechanism for converting between string-based markup generated by JavaServer FACES UI COMPONENTS and server-side Java objects.

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

A framework for building server-side USER interfaces for Web APPLICATIONS WRITTEN in the JAVA programming language.

A framework for building server-side user interfaces for Web applications written in the Java programming language.