J2EE Question: o o o o
J2EE Question: o o o o
J2EE Question: o o o o
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.
5. Is HTML page a web component? - 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.
6. What can be considered as a web component? - 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.
7. What is the 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.
8. What are container services? - A container is a runtime support of a systemlevel entity. Containers provide components with services such as lifecycle
management, security, deployment, and threading.
9. What is the web container? - 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.
10. What is Enterprise JavaBeans (EJB) container? - It manages the execution of
enterprise beans for J2EE applications.
Enterprise beans and their container run on the J2EE server.
11. What is Applet container? - IManages the execution of applets. Consists of a
Web browser and Java Plugin running on the client together.
12. How do we package J2EE components? - J2EE components are packaged
separately and bundled into a J2EE application for deployment. Each component,
its related files such as GIF and HTML files or server-side utility classes, and a
deployment descriptor are assembled into a module and added to the J2EE
application. A J2EE application is composed of one or more enterprise bean,Web,
or application client component modules. The final enterprise solution can use
one J2EE application or be made up of two or more J2EE applications, depending
on design requirements. A J2EE application and each of its modules has its own
deployment descriptor. A deployment descriptor is an XML document with an
.xml extension that describes a components deployment settings.
13. What is a thin client? - A thin client is a lightweight interface to the application
that does not have such operations like query databases, execute complex business
rules, or connect to legacy applications.
14. What are types of J2EE clients? - Following are the types of J2EE clients:
o
o
o
o
Applets
Application clients
Java Web Start-enabled rich clients, powered by Java Web Start
technology.
Wireless clients, based on Mobile Information Device Profile (MIDP)
technology.