J2EE is 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.
2. What is the J2EE module?
A J2EE module consists of one or more J2EE components for the same container type and one component deployment descriptor of that type.
3. What are the components of J2EE application?
A J2EE component is a self-contained functional software unit that is assembled into a J2EE application with its related classes and files and communicates with other components. The J2EE specification defines the following J2EE components:
Application clients and applets are client components.
Java Servlet and JavaServer PagesTM (JSPTM) technology components are web components.
Enterprise JavaBeansTM (EJBTM) components (enterprise beans) are business components.
Resource adapter components provided by EIS and tool vendors.
4. What are the four types of J2EE modules?
1. Application client module
2. Web module
3. Enterprise JavaBeans module
4. Resource adapter module
5. What does application client module contain?
The application client module contains:
--Class files,
--An application client deployment descriptoor.
Application client modules are packaged as JAR files with a .jar extension. 6. What does web module contain?
The web module contains:
--JSP files,
--class files for servlets,
--GIF and HTML files, and
--a Web deployment descriptor. Web modules are packaged as JAR files with a .war (Web ARchive) extension.
7. What are the differences between Ear, Jar and War files? Under what circumstances should we use each one?
There are no structural differences between the files; they are all archived using zip-jar compression. However, they are intended for different purposes.
--Jar files (files with a .jar extension) arre intended to hold generic libraries of Java classes, resources, auxiliary files, etc.
--War files (files with a .war extension) arre intended to contain complete Web applications. In this context, a Web application is defined as a single group of files, classes, resources, .jar files that can be packaged and accessed as one servlet context.
--Ear files (files with a .ear extension) arre intended to contain complete enterprise applications. In this context, an enterprise application is defined as a collection of .jar files, resources, classes, and multiple Web applications.
Each type of file (.jar, .war, .ear) is processed uniquely by application servers, servlet containers, EJB containers, etc.
The Session bean and Entity bean are two main parts of EJB container.
Session Bean
--represents a workflow on behalf of a cliennt
--one-to-one logical mapping to a client. –created and destroyed by a client
--not permanent objects
--lives its EJB container(generally) does noot survive system shut down
--two types: stateless and stateful beans Entity Bean
--represents persistent data and behavior off this data
--can be shared among multiple clients
--persists across multiple invocations
--findable permanent objects
--outlives its EJB container, survives systeem shutdown
--two types: container managed persistence(CCMP) and bean managed persistence(BMP)
9. What is "applet"
A J2EE component that typically executes in a Web browser but can execute in a variety of other applications or devices that support the applet programming model.
10. What is "applet container"
A container that includes support for the applet programming model.
11. What is JSP tag library
A collection of custom tags described via a tag library descriptor and Java classes.
12. What is JSTL
Abbreviate of JavaServer Pages Standard Tag Library.
13. What is JTA
Abbreviate of Java Transaction API.
14. What is JTS
Abbreviate of Java Transaction Service.
15. What is keystore
A file containing the keys and certificates used for authentication
16. What is life cycle (J2EE component)
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.
17. What is life cycle (JavaServer Faces)
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.
18. What is local subset
That part of the DTD that is defined within the current XML file.
19. What is managed bean creation facility
A mechanism for defining the characteristics of JavaBeans components used in a JavaServer Faces application.
20. What is message ?
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.
21. What is authorization?
The process by which access to a method or resource is determined. Authorization depends on the determination of whether the principal associated with a request through authentication is in a given security role. A security role is a logical grouping of users defined by the person who assembles the application. A deployer maps security roles to security identities. Security identities may be principals or groups in the operational environment.
22. What is authorization constraint
An authorization rule that determines who is permitted to access a Web resource collection.
23. What is B2B
B2B stands for Business-to-business.
24. What is backing bean
A JavaBeans component that corresponds to a JSP page that includes JavaServer Faces components. The backing bean defines properties for the components on the page and methods that perform processing for the component. This processing includes event handling, validation, and processing associated with navigation.
25. What is basic authentication
An authentication mechanism in which a Web server authenticates an entity via a user name and password obtained using the Web application's built-in authentication mechanism.
26. What is bean-managed persistence
The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean.
27. What is bean-managed transaction
A transaction whose boundaries are defined by an enterprise bean.
28. What is binding (XML)
Generating the code needed to process a well-defined portion of XML data.
29. What is binding (JavaServer Faces technology)
Wiring UI components to back-end data sources such as backing bean properties.
30. What is build file
The XML file that contains one or more asant targets. A target is a set of tasks you want to be executed. When starting asant, you can select which targets you want to have executed. When no target is given, the project's default target is executed.
31. What is business logic
The code that implements the functionality of an application. In the Enterprise JavaBeans architecture, this logic is implemented by the methods of an enterprise bean.
32.What is business method
A method of an enterprise bean that implements the business logic or rules of an application.
33. What is callback methods
Component methods called by the container to notify the component of important events in its life cycle.
34. What is caller
Same as caller principal.
35. What is caller principal
The principal that identifies the invoker of the enterprise bean method.
36. What is cascade delete
A deletion that triggers another deletion. A cascade delete can be specified for an entity bean that has container-managed persistence.
37. What is CDATA
A predefined XML tag for character data that means "don't interpret these characters," as opposed to parsed character data (PCDATA), in which the normal rules of XML syntax apply. CDATA sections are typically used to show examples of XML syntax.
38. What is certificate authority
A trusted organization that issues public key certificates and provides identification to the bearer.
39. What is client-certificate authentication
An authentication mechanism that uses HTTP over SSL, in which the server and, optionally, the client authenticate each other with a public key certificate that conforms to a standard that is defined by X.509 Public Key Infrastructure.
40. What is comment
In an XML document, text that is ignored unless the parser is specifically told to recognize it.
41. What is commit
The point in a transaction when all updates to any resources involved in the transaction are made permanent.
42. What is component contract
The contract between a J2EE 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.
43. What is component-managed sign-on
A mechanism whereby security information needed for signing on to a resource is provided by an application component.
44. What is connector
A standard extension mechanism for containers that provides 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.
45. What is 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 must support to plug in to a J2EE product-for example, transactions, security, and resource management.
46. What is container
An entity that provides life-cycle management, security, deployment, and runtime services to J2EE components. Each type of container (EJB, Web, JSP, servlet, applet, and application client) also provides component-specific services.
47. What is container-managed persistence
The mechanism whereby data transfer between an entity bean's variables and a resource manager is managed by the entity bean's container.
48. What is container-managed sign-on
The mechanism whereby security information needed for signing on to a resource is supplied by the container.
49. What is container-managed transaction
A transaction whose boundaries are defined by an EJB container. An entity bean must use container-managed transactions.
50. What is content
In an XML document, the part that occurs after the prolog, including the root element and everything it contains.
51. What is context attribute
An object bound into the context associated with a servlet.
52. What is context root
A name that gets mapped to the document root of a Web application.
53. What is 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.
54. What is CORBA
Common Object Request Broker Architecture. A language-independent distributed object model specified by the OMG.
55. What is create method
A method defined in the home interface and invoked by a client to create an enterprise bean.
56. What is credentials
The information describing the security attributes of a principal.
57. What is 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.
58. What is CTS
Compatibility test suite. A suite of compatibility tests for verifying that a J2EE product complies with the J2EE platform specification.
59. What is data
The contents of an element in an XML stream, generally used when the element does not contain any subelements. When it does, the term content is generally used. When the only text in an XML structure is contained in simple elements and when elements that have subelements have little or no data mixed in, then that structure is often thought of as XML data, as opposed to an XML document.
60. What is DDP
Document-driven programming. The use of XML to define applications.
61. What is declaration
The very first thing in an XML document, which declares it as XML. The minimal declaration is . The declaration is part of the document prolog.
62. What is declarative security
Mechanisms used in an application that are expressed in a declarative syntax in a deployment descriptor.
63. What is delegation
An act whereby one principal authorizes another principal to use its identity or privileges with some restrictions.
64. What is deployer
A person who installs J2EE modules and applications into an operational environment.
65. What is deployment
The process whereby software is installed into an operational environment.
66. What is deployment descriptor
An XML file provided with each module and J2EE 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.
67. What is 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.
68. What is digest authentication
An authentication mechanism in which a Web application authenticates itself to a Web server by sending the server a message digest along with 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.
69. What is 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).
67. What is document
In general, an XML structure in which one or more elements contains text intermixed with subelements.
68. What is Document Object Model
An API for accessing and manipulating XML documents as tree structures. DOM provides platform-neutral, language-neutral interfaces that enables programs and scripts to dynamically access and modify content and structure in XML documents.
69. What is document root
The top-level directory of a WAR. The document root is where JSP pages, client-side classes and archives, and static Web resources are stored.
70. What is DTD
Document type definition. An optional part of the XML document prolog, as specified by the XML standard. The DTD specifies constraints on the valid tags and tag sequences that can be in the document. The DTD has a number of shortcomings, however, and this has led to various schema proposals. For example, the DTD entry says that the XML element called username contains parsed character data-that is, text alone, with no other structural elements under it. The DTD includes both the local subset, defined in the current file, and the external subset, which consists of the definitions contained in external DTD files that are referenced in the local subset using a parameter entity.
71. What is 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, the JMS provider retains the subscription's messages until they are received by the subscription or until they expire.
72. What is EAR file
Enterprise Archive file. A JAR archive that contains a J2EE application.
73. What is ebXML
Electronic Business XML. A group of specifications designed to enable enterprises to conduct business through the exchange of XML-based messages. It is sponsored by OASIS and the United Nations Centre for the Facilitation of Procedures and Practices in Administration, Commerce and Transport (U.N./CEFACT).
74. What is EJB
Enterprise JavaBeans.
75. What is 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, transactions, deployment, naming, and other services. An EJB container is provided by an EJB or J2EE server.
76. What is EJB container provider
A vendor that supplies an EJB container.
77. What is EJB context
A vendor that supplies an EJB container. 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.
78. What is 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
79. What is EJB JAR file
A JAR archive that contains an EJB module.
80. What is EJB module
A deployable unit that consists of one or more enterprise beans and an EJB deployment descriptor.
81. What is 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.
82. What is EJB server
Software that 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 it does not specify the contract between these two entities. An EJB server can host one or more EJB containers.
83. What is EJB server provider
A vendor that supplies an EJB server.
83. What is EJB server provider What is element
A unit of XML data, delimited by tags. An XML element can enclose other elements.
84. What is empty tag
A tag that does not enclose any content
85. What is enterprise bean
A J2EE component that implements a business task or business entity and is hosted by an EJB container; either an entity bean, a session bean, or a message-driven bean.
86. What is enterprise bean provider
An application developer who produces enterprise bean classes, remote and home interfaces, and deployment descriptor files, and packages them in an EJB JAR file.
87. What is enterprise information system
The applications that constitute an enterprise's existing system for handling companywide 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 or remote interfaces or both. Examples of enterprise information systems include enterprise resource planning systems, mainframe transaction processing systems, and legacy database systems.
91. What is an entity
A distinct, individual item that can be included in an XML document by referencing it. Such an entity reference can name an entity as small as a character (for example, <, which references the less-than symbol or left angle bracket, <). An entity reference can also reference an entire document, an external entity, or a collection of DTD definitions.
92. What is entity bean An enterprise bean that represents persistent data maintained in a database.
An entity bean can manage its own persistence or 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.
