အတိအက်ၾကီးမွတ္မိဖုိ႕မလုိပါဘူး။ အေရးၾကီးတာေလးေတြမွတ္မိရင္မဆိုးလွဘူး။ highlight လုပ္ထားတာေတြကေတာ႔ က်က္ထားတုန္းက ေမ႔ေနတာေတြထင္တယ္။ အခုေတာ႔မမွတ္မိေတာ႔ဘူး။
Question: What
do you understand by a J2EE module?
Answer: A J2EE module is a software unit that consists of one or more J2EE components of the same container type along with one deployment descriptor of that type. J2EE specification defines four types of modules:
Web
application client and
resource adapter
Answer: A J2EE module is a software unit that consists of one or more J2EE components of the same container type along with one deployment descriptor of that type. J2EE specification defines four types of modules:
Web
application client and
resource adapter
EJB
//
a) Client-tier components run on the client machine.
b) Web-tier components run on the J2EE server.
c) Business-tier components run on the J2EE server and the
d) Enterprise information system (EIS)-tier software runs on the EIS servers
b) Web-tier components run on the J2EE server.
c) Business-tier components run on the J2EE server and the
d) Enterprise information system (EIS)-tier software runs on the EIS servers
//
Question: Why do understand by a container?
Answer: Normally, thin-client multi-tiered applications are hard to write because they involve many lines of intricate code to handle transaction and state management, multithreading, resource pooling, and other complex low-level details. The component-based and platform-independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components. In addition, the J2EE server provides underlying services in the form of a container for every component type. Because you do not have to develop these services yourself, you are free to concentrate on solving the business problem at hand (Source:http://java.sun.com/j2ee/1.3/docs/tutorial/doc/Overview4.html ).
In short containers are the interface between a component and the low-level platform specific functionality that supports the component. The application like Web, enterprise bean, or application client component must be assembled and deployed on the J2EE container before executing.
Answer: Normally, thin-client multi-tiered applications are hard to write because they involve many lines of intricate code to handle transaction and state management, multithreading, resource pooling, and other complex low-level details. The component-based and platform-independent J2EE architecture makes J2EE applications easy to write because business logic is organized into reusable components. In addition, the J2EE server provides underlying services in the form of a container for every component type. Because you do not have to develop these services yourself, you are free to concentrate on solving the business problem at hand (Source:http://java.sun.com/j2ee/1.3/docs/tutorial/doc/Overview4.html ).
In short containers are the interface between a component and the low-level platform specific functionality that supports the component. The application like Web, enterprise bean, or application client component must be assembled and deployed on the J2EE container before executing.
// Question: What are the services provided by a
container?
Answer: The services provided by container are as follows:
a) Transaction management for the bean
b) Security for the bean
c) Persistence of the bean
d) Remote access to the bean
e) Lifecycle management of the bean
f) Database-connection pooling
g) Instance pooling for the bean
Answer: The services provided by container are as follows:
a) Transaction management for the bean
b) Security for the bean
c) Persistence of the bean
d) Remote access to the bean
e) Lifecycle management of the bean
f) Database-connection pooling
g) Instance pooling for the bean
// Question: What are types of J2EE clients?
Answer: J2EE clients are the software that access the services components installed on the J2EE container. Following are the J2EE clients:
a) Applets
b) Java-Web Start clients
c) Wireless clients
d) Web applications
Answer: J2EE clients are the software that access the services components installed on the J2EE container. Following are the J2EE clients:
a) Applets
b) Java-Web Start clients
c) Wireless clients
d) Web applications
// What is Java Naming and Directory Service? - 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.
directory services such as LDAP, NDS, DNS, and NIS.
What is Struts? - A Web page development framework, a MVC
framework. Struts combines Java Servlets, Java Server Pages, custom tags, and message resources into a unified framework. It is
a cooperative, synergistic platform, suitable for
development teams, independent developers, and everyone between.
What is JAAS? - 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.
What is J2EE Connector? - 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.
No comments:
Post a Comment