B.C.

SANGEETHA

MIDDLEWARE TECHNOLOGIES

MIDDLEWARE TECHNOLOGY IMPORTANT QUESTIONS

(5 and 10 MARKS)
1. Architecture of .net in detail?

.NET is tiered, modular, and hierarchal. Each tier of the .NET Framework is a layer of
abstraction. .NET languages are the top tier and the most abstracted level.
The common language runtime is the bottom tier, the least abstracted, and closest to the
native environment. This is important since the common language runtime works closely
with the operating environment to manage .NET applications.
The .NET Framework is partitioned into modules, each with its own distinct responsibility.
Finally, since higher tiers request services only from the lower tiers, .NET is hierarchal.
What is the .NET Framework? ???

B.C.SANGEETHA

MIDDLEWARE TECHNOLOGIES

The .NET Framework is a new and revolutionary platform created by Microsoft for developing
applications.
It is a platform for application developers.
It is a Framework that supports Multiple Language and Cross language integration.
IT has IDE (Integrated Development Environment).
Framework is a set of utilities or can say building blocks of your application system.
.NET Framework provides GUI in a GUI manner.
.NET is a platform independent but with help of Mono Compilation System (MCS). MCS
is a middle level interface.
.NET Framework provides interoperability between languages i.e. Common Type
System (CTS)
.NET Framework also includes the .NET Common Language Runtime (CLR), which is
responsible for maintaining the execution of all applications developed using the .NET
library.
The .NET Framework consists primarily of a gigantic library of code.

2.Explain lifecycle of Stateless session bean and Stateful session bean?

In this section of EJB tutorial, we will learn about the lifecycle of Stateful and Stateless Session
Beans.
Stateless Session Bean Life cycle
There are two stages in the Lifecycle of Stateless Session Bean. These are:
a) Does Not Exist
In the Does Not Exist stage, bean does not have instance in the memory. In this stage bean
has not been instantiated.
b) Method Ready Pool
In the Method Ready Pool stage bean has instance(s) in the memory of the EJB container and
it is ready to serve clients. On the startup of the EJB container some instances of the bean are
created and placed in the pool. EJB container creates the new instance of the Bean and then
sets the session context (setSessioncontext()) and it calls the ejbCreate() method to place the
bean in the Method Ready Pool stage. Container calls the ejbRemove() method to move the
bean into Does Not Exist state.
Following Diagram shows the Life cycle of Stateless Session Bean

B.C.SANGEETHA

MIDDLEWARE TECHNOLOGIES

Stateful Session Bean Life cycle

There are there stages in the life cycle of Stateful Session bean Life cycle. These are:
a) Does Not Exist
This is the Does Not Exist stage, bean does not have instance in the memory. In this stage
bean has not been instantiated.
b) Method Ready Pool
In the Method Ready Pool stage bean has instance in the memory of the EJB container and it
is ready to serve client. One instance of the Stateful Session Bean servers only one client.
When Client Calls create(args) method on the Home Interface, server creates new instance of
the bean and sets the Session Context and then container calls the ejbCreate(args) method on
the bean and places the bean into Method Ready Pool stage. ejbRemove or Timeout moves the
bean into Does Not Exist stage.
c) Passive state
In the Passive state the bean is passivated to conserve the resource. The passivate method is
called before the instance enters the "passive" state. The instance should release any
resources that it can re-acquire later in the ejbActivate() method. After the passivate method
completes, the instance must be in a state that allows the container to use the Java Serialization
protocol to externalize and store away the instance's state. ejbRemove or Timeout moves the
bean into Does Not Exist stage.

B.C.SANGEETHA

MIDDLEWARE TECHNOLOGIES

Following Diagram shows the Life cycle of Statelful Session Bean

B.C.SANGEETHA

MIDDLEWARE TECHNOLOGIES

2.Applications domain in .NET?

An Application Domain is a light weight process and provides a logical and physical
isolation from another .NET application.
This ensures that the Applications can work independent and isolated of each other. An
Application Domain is created by the Common Language Runtime (CLR) and it ensures
that if one Application Domain crashes or goes down, it does not in any way effect the
functioning of another Application Domain.
Multiple .NET applications can be executed in one single process by loading these
applications in separate Application Domains. Several threads can be executing in a
single application domain at any given time and a particular thread is not confined to a
single application domain. In other words, threads are free to cross application domain
boundaries and a new thread is not created for each application domain.

B.C.SANGEETHA

MIDDLEWARE TECHNOLOGIES