Home Java

Core Java Java SE 6 Advanced Java JSP Servlets JDBC EJB Web Services J2ME JSTL Hibernate Struts 1.x Struts 2 JSF JavaFX Ajax Spring 2.5 Spring 3

Frameworks

DOJO iBatis Flex 3 Flex 4 SQL MySQL GPS WiMaX VoIP WiFi HSDPA WAP EAI HTML Java Script DBUNIT ANT Maven JUNIT Jmeter Servers for Java Tomcat Apache Geronimo Jboss PHP Tutorial Starting PHP PHP MySQL Zend FrameWork

Database

Technology

Web Development

Build/Test Tools

Servers

PHP

Home Ejb Application Server

Top of Form

partner-pub-0714 FORID:10

Search

w w w .roseindia.n

Bottom of Form

Application Server Posted on: May 23, 2009 at 12:00 AM An application server is an application program that accepts connections in order to service requests, by sending back responses.

Application Server
An application server is an application program that accepts connections in order to service requests, by sending back responses. An application server can run remotely (connected to client through a computer network) or can exist on the same computer where the client application is running. Examples include file server, database server, backup server, print server, mail server, web server, FTP server, application server, VPN server, DHCP server, DNS server, WINS server, logon server, security server, domain controller, backup domain controller, proxy server, firewall, etc. Application server are developed to support the quick development of the enterprise applications. They provide security and state maintenance with the data base and persistence. An application server may be a part of a three tier architecture model. A three tier architecture includes the Client Tier, Middle Tier and the EIS (Enterprise Information System) Tier. It may consists of Presentation Tier (as the GUI interface), Middle Tier as the collection of business logic application and the EIS (Enterprise Information System). The view tier is nothing but the web based graphical user interface to interact with the clients, Middle tier is the combination of web containers and the EJB containers. EIS contains persistence and the database management systems to support the applications. JEE Platform requires database to store the business data. This database is accessible by means of JDBC, JDO or the SQLJ APIs. We can also access the database through enterprise beans, web components and the application client components.

Related Tags for Application Server: c, com, server, application, network, io, remote, client, cli, app, connect, computer, ie, cte, where, work, to, run, e, can, li, put, in, m, nt, net, ca, net, cl, through, running, em, compute, me, hr, pp, cat, same, s, etw, at, k, is, connected, sa, rv, tw, xi, s, sam, s, sam, th, st, ati, ap, exi, ica, ica, pl, on, om, o

Enterprise beans are the Java EE server side components that run inside the ejb container and encapsulates the business logic of an enterprise application.

Enterprise Beans
Enterprise beans are the Java EE server side components that run inside the ejb container and encapsulates the business logic of an enterprise application. Enterprise applications are the software applications developed intended to use at large scale. These applications involves large number of data accessing concurrently by many users. Enterprise beans are used to perform various types of task like interacting with the client, maintaining session for the clients retrieving and holding data from the database and communicating with the server. Benefits of enterprise beans: Enterprise beans are widely used for developing large and distributed applications. EJB container provides the system-level services (like transaction management and security authorization) to the enterprise beans. These services simplifies the development process of large and distributed applications and the developer just have to concentrate on solving the problem occurred in it. The client developer can focus only on the representation style of the client as all the business logic of the application is contained in the enterprise beans. The client developer does not bother about the code that implements business logic or the logic to access the databases. This means that the clients are thinner. It benefits the client to be thin because the client runs on the small devices. Developing new applications from the existing beans is much easier because the enterprise beans are portable components. That means applications developed by using the enterprise components can run on any complaint J2EE server. When to use the enterprise beans: Some of the points are illustrated below that signifies the use of enterprise beans. Applications developed by using the enterprise beans deal with a variety of clients, simply by writing few lines of code, so that the client can locate the enterprise beans. The client locating the enterprise bean may be various, numerous and thin. Enterprise beans support transaction to ensure the integrity of the database. Transaction is the mechanism of managing the concurrent access of shared objects. Managing the fast growing number of users requires distributed application components across multiple machines means that the application must be scalable.

Types of enterprise beans: EJB 3.0 defines two types of enterprise beans. These are:
1. Session bean: These types of beans directly interact with the client and contains business

logic of the business application.

2. Message driven bean: It works like a listener or a consumer for a particular messaging

service such as Java Message API or JPA for short.

Features of EJB 3.0

Now its time to look over the new features of EJB 3.0 that provides some simplification over the previous EJB API. There are various simplification made in EJB 3.0 like:
No need of home and object interface. No need of any component interface. Made use of java annotations. Simplifies APIs to make flexible for bean's environment.

Now we will discuss all the above aspects of EJB3.0 that makes the EJB programming model simple and more efficient. Elimination of Home and Remote Interfaces: Deprecation of home and remote interfaces simplifies the development. The new session beans contain all the business methods inside the business interface. The bean provider designates the business interface as local business interface or the remote business interface or both according to the client whether it is local or remote. Business methods on remote interface can throw arbitrary application exceptions, while they are not allowed to throw java.rmi.RemoteException. While in case of EJB 2.1 all the methods of home and object interface throws the java.rmi.RemoteException. Package javax.ejb.EJBException encapsulates exceptions such as protocols, system level problems, or otherwise that the container returns to the client. Since EJBException is the subclass of the java.rmi.RemoteException therefore we did not include it in throws clause of business methods. A message driven bean does not need to include the business interface as there is no direct interaction of the client with the message driven bean. Whenever a MDB has an unexpected problem then the container logs the error and communicate it with the help of javax.ejb.EJBException to the corresponding resource adapter rather than the client. Elimination of Component Interface: Component interface in EJB2.1 or in earlier versions are used to provide a way through which the container notifies the bean instances of various life cycles they are affecting it. The previous versions of the component interface are used to stay in the events in its lifecycle. These component interfaces includes the various life cycles methods implemented by the bean class. The container used to call the appropriate method of the component interface to handle the bean's instance life cycle events according to the way it wants. For example, the container notifies the message driven bean instance that it is about to destroy, simply by invoking ejbDestroy() method on the corresponding class of the message driven bean. Bean class can close the JDBC database connection within the ejbDestroy() method to free up the resources. Similarly the container that is going to associate a client in case of stateful notifies the bean instance by calling the ejbCreate() method on the bean class and the bean class instantiates the bean instance. Consider the situation, when the bean does not receive the notification from the container about its life cycle's methods then the bean has to implement the component interfaces regardless whether it is needed or not. In case of session bean, the bean class does not need to implement the javax.ejb.SessionBean or javax.ejb.MessageDrivenBean in case of message driven bean. Now the next question that arises is that how a bean class get notified by the container if it is interested? The solution is that there are two ways to do so, the first one is, the bean provider can implement a separate bean class that consists of all the callback notification methods that inform the container to treat it as a listener class. The second way is that, a bean provider can implement the notification method inside the bean class and designate this method to handle the corresponding events In both the cases bean class uses annotations. Annotations are the

additional key features of EJB 3.0 specifications. To know about the annotation just click on the link annotations. Simplified Access to Environment: Almost all the EJBs are required to access the environment to gain access to external resources, enterprise beans and other entries like properties. To get hold of these entries EJB mainly relies on JNDI API. EJB 3.0 also includes the features like lookup method on the EJBContest and dependency injection to access the bean's dependencies. Dependency Injection: Dependency injection is the mechanism through which the container injects the requested environmental entry to make available to the bean instance before any bean instance is invoked on that particular instance. Then the container injects these entries into bean variables or methods. It is bean provider's duty to tell the container that which method or variables should be injected at runtime. The bean provider can do this by using the deployment descriptor or annotations. Bean methods used for dependency injection should follow the java naming convention for properties in that they should follow the setXXX() convention. Consider the situations like dependency injection fails due to some reasons, the container can not make available the environmental entries due to which the bean is functioning properly, in such situations the container discards the bean instances and creates new instances. EJB Context: Bean must know about its environment at runtime such as security principle, transaction context in which its method is invoked and so on. javax.ejb.EJBContext API works like a window for the bean to the outside world through which it is interacting to the container. EJBContext is further categorized into SessionContext and MessageDrivenContext for the session beans and message driven beans respectively. Bean instances may use the dependency injection to access EJBContext instance. Another way through which a JNDI accesses the environment variables is the lookup() method of the EJBContext interface. Bean must use the JNDI API to access the environmental dependencies. Enhanced Lifecycle Methods and Callback Listener Classes: EJB 3.0 does not enforce to implement all unnecessary callback methods but can designate any other method to receive the notification for life cycle events. We can also use the callback listener class instead of callback methods defined in the same bean class. Interceptors: An intercept is a method used to intercept a business method invocation. Stateless session beans, Stateful session beans and message driven beans may includes the interceptors. We can also define an interceptor class instead of defining the interceptor methods in the bean class. Simple JNDI lookup of EJB: Lookup of the EJB has been simplified so that the client can directly invoke methods on EJB rather than creating the bean instance simply by invoking create method on EJB.

Annotations
Sun Microsystem added the features like annotation to make the development easier and more efficient in jdk 5. The main objective to develop the annotations is to make the development easier. Annotations behaves like the meta. The literal meaning of meta data is data about data. Java also signifies this meaning. Annotations are like meta data, means you are free to add your code and can also apply them to variables, parameters, fields type declarations, methods and

constructors. Metadata is also used to create the documentation to perform rudimentary compile time checking and even for tracking down the dependencies in code. XDoclet contains all these features and is widely used. Annotations provide a means of indicating about methods, classes, dependencies, incompleteness and also about the references on other methods and classes respectively. Quoting from Sun's official site, "It (annotation-based development) lets us avoid writing boilerplate code under many circumstances by enabling tools to generate it from annotations in the source code. This leads to a declarative programming style where the programmer says what should be done and tools emit the code to do it." Annotation is the way of associating the program elements with the meta tags so that the compiler can extract program behavior to support the annotated elements to generate interdependent code when necessary. Fundamentals of annotations While going through the annotations you should consider two things. The first one is the "annotation" itself and second one is the "annotations types". An annotation is the meta tag, used to give some life to the code you are using. While annotation type is used to define annotations so that you can use them while creating your own custom annotations. An annotation type definition appends an "at" @ sign at the start of the interface keyword with the annotation name. On the other hand, an annotation includes the "at" @ sign followed by the annotation type. You can also add the data within the parenthesis after the annotation name. Lets illustrate the concept more clearly by using some examples. Defining an annotation (Annotation type) public @interface Example { String showSomething(); } Annotating the code (Annotation) Example (showSomething="Hi! How r you") public void anymethod() { .... } Annotation Types: Three types of annotations types are there in java.

Marker: Like the marker interface, marker annotations does not contain any elements except the name itself. The example given below clarifies the concept of marker interface. Example: public @interface Example{ } Usage: @Example public void anymethod() { -----------}

Single-value: This type of elements provide only single value. It means that these can be represented with the data and value pair or we can use the shortcut syntax (just by using the value only within the parenthesis). Example: public @interface Example{ String showSomething(); } Usage: @Example ("Hi ! How r you") public void anymethod(){ -------}

Multi-value or Full-value: These types of annotations can have multiple data members. Therefore use full value annotations to pass the values to all the data members. Example: public @interface Example{ String showSomething(); int num; String name; } Usage: @Example (showSomething = "Hi! How r you", num=5, name="zulfiqar" ) public void anymethod{ // code here }

Rules defining the Annotation type: Here are some rules that one should follow while defining and using annotations types Start the annotation declaration starting with the symbol "at" @ following the interface keyword that should follow the annotation name. Method declaration should not throw any exception. Method declaration should not contain any parameter. Method using annotations should return a value, one of the types given below: String primitive enum Class array of the above types

Annotations: JDK 5 (Tiger) contains two types of annotations:

Simple annotations: These types of annotations are used to annotate the code only. We can not use these types of annotations for creating the custom annotation type. Meta annotations: Also known as annotations of annotations are used to annotate the annotation-type declaration. Override Depricated Suppresswarnings

Simple annotations: JDK 5 includes three types of simple annotations.

JDK 5 (also known as Tiger) does not include many built-in annotations but it facilitates to core java to support annotation features. Now will discuss in brief each of the above simple annotation types along with examples. Override annotation: The override annotation ensures that the annotated method is used to override the method in the super class. If the method containing this type of annotation does not override the method in the super class then the compiler will generate a compile time error. Lets take an example and demonstrate what will happen if the annotated method does not override the method in the super class. Example 1: public class Override_method{ @Override public String toString(){ return super.toString() + "Will generate an compile time error."; } } Suppose there is spell mistake in the method name such as the name is changed from toString to toStrimg. Then on compiling the code will generate the message like this: Compiling 1 source file to D:tempNew Folder (2) TestJavaApplication1buildclasses D:tempNew Folder (2)TestJavaApplication1srctest myannotationTest_Override.java:24: method does not override a method from its superclass @Override 1 error BUILD FAILED (total time: 0 seconds) Deprecated annotation: These types of annotations ensure that the compiler warns you when you use the deprecated element of the program. The example given below illustrates this concept. Example: Lets first create the class containing the deprecated method. public class Deprecated_method{ @Deprecated public void showSomething() { System.out.println("Method has been depricated'");

} } Now lets try to invoke this method from inside the other class: public class Test_Deprication { public static void main(String arg[]) throws Exception { new Test_Deprication(); } public Test_Deprication() { Deprecated_method d = new Deprecated_method(); d.showSomething(); } The method showSomething() in the above example is declared as the deprecated method. That means we can't further use this method any more. On compiling the class Depricated_method does not generate any error. While compiling the class Test_Deprication generates the message like this: Compiling 1 source file to D:tempNew Folder (2)TestJavaApplication1buildclasses D:tempNew Folder (2)TestJavaApplication1srctestmyannotation Test_Deprication.java:27: warning: [deprecation] showSomething() in test.myannotation.Deprecated_method has been deprecated d.showSomething(); 1 warning The Suppresswarning annotation: These types of annotations ensure that the compiler will shield the warning message in the annotated elements and also in all of its sub-elements. Lets take an example: Suppose you annotate a class to suppress a warning and one of its method to suppress another warning, then both the warning will be suppressed at the method level only. Lets demonstrate it by an example: public class Test_Depricated { public static void main(String arg[]) throws Exception { new TestDepricated().showSomething(); } @SuppressWarnings({"deprecation"}) public void showSomething() { Deprecation_method d = new Deprecation_method(); d.showSomething(); } } This example is suppressing the deprecation warnings that means we can't see the warnings any more. Note: Applying annotation at most deeply nested elements is a good idea. It is better to apply annotations at the method level rather than the class to annotate a particular method.

Meta-Annotations (Annotation Types): There are four types ofm Meta annotations (or annotations of annotations) defined by the JDK 5. These are as follows: Target Retention Documented Inherited

Target annotation: Target annotation specifies the elements of a class to which annotation is to be applied. Here is the listing of the elements of the enumerated types as its value: @Target(ElementType.TYPE)?applicable to any element of a class. @Target(ElementType.FIELD)?applicable to field or property. @Target(ElementType.PARAMETER)?applicable to the parameters of a method. @Target(ElementType.LOCAL_VARIABLE)?applicable to local variables. @Target(ElementType.METHOD)?applicable to method level annotation. @Target(ElementType.CONSTRUCTOR)?applicable to constructors. @Target(ElementType.ANNOTATION_TYPE)?specifies that the declared type itself is an annotation type.

Here is an example that demonstrates the target annotation: Example: @Target(ElementType.METHOD) public @interface Test_Element { public String doTestElement(); } Now lets create a class that use the Test_Element annotation: public class Test_Annotations { public static void main(String arg[]) { new Test_Annotations().doTestElement(); } @Test_Target(doTestElement="Hi ! How r you") public void doTestElement() { System.out.printf("Testing Target Element annotation"); } } The @Target(ElementType.METHOD) specifies that this type of annotation can be applied only at method level. Compiling and running the above program will work properly. Lets try to apply this type of annotation to annotate an element: public class Test_Annotations { @Test_Target(doTestElement="Hi! How r you") private String str; public static void main(String arg[]) { new Test_Annotations().doTestElement(); }

public void doTestElement() { System.out.printf("Testing Target Element annotation"); } } Here we are trying to apply @Target(ElementType.METHOD) at the field level by declaring the element private String str; after the @Test_Target(doTestElement="Hi ! How r you") statement. On compiling this code will generate an error like this: "Test_Annotations.java": D:R_AND_DTest_Annotationsrctestmyannotation Test_Annotations.java:16: annotation type not applicable to this kind of declaration at line 16, column 0 @Test_Target(doTestElement="Hi ! How r you") ^ Error in javac compilation Retention annotation: These types of annotation specify where and how long annotation with this types are to be retained. There are three type of Retention annotations are of three types.

RetentionPolicy.SOURCE: This type of annotation will be retained only at source level and the compiler will ignore them. RetentionPolicy.CLASS: This type of annotation will be retained at the compile time the virtual machine (VM) will ignore them. RetentionPolicy.RUNTIME: Virtual machine will retained the annotation of this type and they can be read only at run-time.

Lets demonstrate that how this type of annotations are applied by taking an example using RetentionPolicy.RUNTIME. Example: @Retention(RetentionPolicy.RUNTIME) public @interface Retention_Demo { String doRetentionDemo(); } This example uses the annotation type @Retention(RetentionPolicy.RUNTIME) that indicates the VM will retained your Retention_Demo annotation so that it can be read effectively at runtime. Documented annotation: This type of annotation should be documented by the javadoc tool. javadoc does not include the annotation by default. Include the annotation type information by using @Documented in the generated document. In this type of annotation all the processing is done by javadoc-like tool. The given example demonstrates the use of the @Documented annotations. Example: @Documented public @interface Documented_Demo { String doTestDocumentedDemo();

} Next, make changes in Test_Annotations class as follows: public class Test_Annotations { public static void main(String arg[]) { new Test_Annotations().doTestRetentionDemo(); new Test_Annotations().doTestDocumentedDemo(); } @Retention_Demo (doTestRetentionDemo="Hello retention annotation") public void doTestRetentionDemo() { System.out.printf("Testing 'Retention' annotation"); } @Documented_Demo (doTestDocumentedDemo="Hello Test documentation") public void doTestDocumentedDemo() { System.out.printf("Testing 'Documented' annotation"); } } Inherited Annotation: This annotation is little bit complex. It inherits the annotated class automatically. If you specify @Inherited tag before defining a class then apply the annotation at your class and finally extend the class then the child class inherits the properties of the parent class automatically. Lets demonstrate the benefits of using the @Inherited tag by an example: Example: Lets first, define the annotation: @Inherited public @interface ParentObjectDemo { boolean isInherited() default true; String showSomething() default "Show anything?"; } Now, annotate the class with our annotation: @ParentObjectDemo public Class ChildObjectDemo { } The above example shows that you do not need to define the interface methods inside the implemented class. The @Inherited tag automatically inherits the methods for you. Suppose you define the implementing class in the old-fashioned-java-style then let us see the effect of doing this: public class ChildObjectDemo implements ParentObjectDemo { public boolean isInherited() { return false; } public String showSomething() { return "";

} public boolean equals(Object obj) { return false; } public int hashCode() { return 0; } public String toString() { return ""; } public Class annotationType() { return null; } } Have you seen the difference? You have to implement all the methods of the parent interface. You will have to implement the equals(), toString(), and the hashCode() methods of the Object class and also the annotation type method of the java.lang.annotation.Annotation class. You will also have to include all these methods in your class regardless of whether you are implementing all these methods or not. A session bean is the enterprise bean that directly interact with the user and contains the business logic of the enterprise application.

Session Beans
What is a Session bean A session bean is the enterprise bean that directly interact with the user and contains the business logic of the enterprise application. A session bean represents a single client accessing the enterprise application deployed on the server by invoking its method. An application may contain multiple sessions depending upon the number of users accessing to the application. A session bean makes an interactive session only for a single client and shields that client from complexities just by executing the business task on server side. For example, whenever a client wants to perform any of these actions such as making a reservation or validating a credit card, a session bean should be used. The session bean decides what data is to be modified. Typically, the session bean uses an entity bean to access or modify data. They implement business logic, business rules, algorithms, and work flows. Session beans are relatively short-lived components. The EJB container may destroy a session bean if its client times out. A session bean can neither be shared nor can persist (means its value can not be saved to the database) its value. A session bean can have only one client. As long as the client terminates, session bean associated with this client is also terminated and the data associated with this bean is also destroyed.

The above figure shows how Session Bean interacts with the clients as well as with the Entity Beans. Session beans are divided into two parts.

Stateless Session Beans: A stateless session bean does not maintain a conversational state with the client. When a client invokes the methods of a stateless bean, the instance of bean variables may contain a state specific to that client only for the duration of a method invocation. Once the method is finished, the client-specific state should not be retained i.e. the EJB container destroys a stateless session bean. These types of session beans do not use the class variables (instance variables). So they do not persist data across method invocation and therefore there is no need to passivates the bean's instance. Because stateless session beans can support multiple clients, they provide the better scalability for applications that require large numbers of clients. Stateful Session Beans: These types of beans use the instance variables that allows the data persistent across method invocation because the instance variables allow persistence of data across method invocation. The client sets the data to these variables which he wants to persist. A stateful session bean retains its state across multiple method invocations made by the same client. If the stateful session bean's state is changed during a method invocation, then that state will be available to the same client on the following invocation. The state of a client bean is retained for the duration of the client-bean session. Once the client removes the bean or terminates, the session ends and the state disappears. Because the client interacts with its bean, this state is often called the conversational state.

For example, consider a customer using a debit card at an ATM machine. The ATM could perform various operations like checking an account balance, transferring funds, or making a withdrawal. These operations could be performed one by one, by the same customer. So the bean needs to keep track its state for each of these operations to the same client. Thus Stateful session beans has the extra overhead for the server to maintain the state than the stateless session bean. The user interface calls methods of session beans if the user wants to use the functionality of the session bean. Session beans can call to other session beans and entity beans. When to use session beans: Generally session beans are used in the following circumstances: When there is only one client is accessing the beans instance at a given time. When the bean is not persistent that means the bean is going to exist no longer. The bean is implementing the web services. What the bean wants to holds information about the client across method invocation. When the bean works as the mediator between the client and the other component of the application. When the bean have to manage the work flow of several other enterprise beans. If the bean does not contain the data for a specific client. If there is only one method invocation among all the clients to perform the generic task.

Stateful session beans are useful in the following circumstances:

Stateless session beans are appropriate in the circumstances illustrated below:

Life Cycle of a Stateless Session Bean: Since the Stateless session bean does not passivates across method calls therefore a stateless session bean includes only two stages. Whether it does not exist or ready for method invocation. A stateless session bean starts its life cycle when the client first obtains the reference of the session bean. For this, the container performs the dependency injection before invoking the annotated @PreConstruct method if any exists. After invoking the annotated @PreConstruct method the bean will be ready to invoke its method by the client.

The above figure demonstrates how the Stateless Session Beans are created and destroyed.

The container calls the annotated @PreDestroy method while ending the life cycle of the session bean. After this, the bean is ready for garbage collection. Life Cycle of a Stateful Session Bean: A Stateful session bean starts its life cycle when the client first gets the reference of a stateful session bean. Before invoking the method annotated @PostConstruct the container performs any dependency injection after this the bean is ready. The container may deactivate a bean while in ready state (Generally the container uses the least recently use algorithm to passivates a bean). In the passivate mechanism the bean moves from memory to secondary memory. The container invokes the annotated @PrePassivate method before passivating the bean. If a client invokes a business method on the passivated bean then the container invokes the annotated @PostActivate method to let come the bean in the ready state.

The above image shows the various states of the Stateful Session Beans While ending the life cycle of the bean, the client calls the annotated @Remove method after this the container calls the annotated @PreDestroy method which results in the bean to be ready for the garbage collection.

Stateless Session Bean Example

In this part of Enterprise Session Beans, you will learn how to develop, deploy, and run a simple Java EE application named example using stateless session bean. The purpose of example is to performs the mathematical operations such as Addition, Subtraction, Multiplication, and Division. The example application consists of an enterprise bean, which performs the calculations, and two types of clients: an application client and a web client.

There are following steps that you have to follow to develop a example JEE application. 1. Create the enterprise bean: CalculatorBean 2. Create the web client: WebClient 3. Deploy example onto the server. 4. Using a browser, run the web client. I. Creating the enterprise bean: The enterprise bean in our example is a stateless session bean called CalculatorBean. The source code for CalculatorBean is in ?net/roseindia/ejb3/stateless? directory. Creating CalculatorBean requires these steps: (i) Coding the bean?s Remote business interface and Enterprise bean class. (ii) Compiling the source code with the Ant tool. (i) Coding the Business Interface The business interface defines the business methods that a client can call remotely. The business methods are implemented in the enterprise bean class. The source code for the CalculatorRemote business interface is given below.
package net.roseindia.ejb3.stateless; import java.math.*; import javax.ejb.Remote; import java.lang.annotation.*; @Remote public interface CalculatorRemote { public float add(float x, float y); public float subtract(float x, float y); public float multiply(float x, float y); public float division(float x, float y); }

Note that, the @Remote annotation decorating the interface definition. This lets the container know that CalculatorBean will be accessed by remote clients. II. Coding the Enterprise Bean Class The enterprise bean class for this example is called CalculatorBean. This class implements the four business methods (add, subtract, multiply, division) that are defined in the CalculatorRemote business interface. The source code for the CalculatorBean class is given below.
package net.roseindia.ejb3.stateless; import java.math.*; import javax.ejb.Stateless; import javax.ejb.Remote; @Stateless(name="CalculatorBean") @Remote(CalculatorRemote.class) public class CalculatorBean implements CalculatorRemote{

public float add(float x, float y){ return x + y; } public float subtract(float x, float y){ return x - y; } public float multiply(float x, float y){ return x * y; } public float division(float x, float y){ return x / y; } }

Note that, the @Stateless annotation decorating the enterprise bean class. This lets the container know that CalculatorBean is a stateless session bean.
Compiling and Packaging the example Example

Now you are ready to compile the remote business interface (CalculatorRemote.java), the enterprise bean class (CalculatorBean.java) and the application client (CalculatorClient.java), then package the compiled classes into an enterprise bean JAR. II. Creating the calculator Web Client The web client is contained in the JSP page "WebClient.jsp". A JSP page is a text-based document that contains JSP elements, which construct dynamic content, and static template data, expressed in any text-based format such as HTML, WML, and XML. The source code for the ?form.jsp? is given below.
<html> <head> <title>Calculator</title> </head> <body bgcolor="pink"> <h1>Calculator</h1> <hr> <form action="WebClient.jsp" method="POST"> <p>Enter first value: <input type="text" name="num1" size="25"></p> <br> <p>Enter second value: <input type="text" name="num2" size="25"></p> <br>

<b>Seclect your choice:</b><br> <input type="radio" name="group1" value ="add">Addition<br> <input type="radio" name="group1" value ="sub">Subtraction<br> <input type="radio" name="group1" value ="multi">Multiplication<br> <input type="radio" name="group1" value ="div">Division<br> <p> <input type="submit" value="Submit"> <input type="reset" value="Reset"></p> </form> </body> </html>

The following statements given below in ?WebClient.jsp? are used for locating the business interface, creating an enterprise bean instance, and invoking a business method.
InitialContext ic = new InitialContext(); CalculatorRemote calculator = (CalculatorRemote)ic.lookup("example/CalculatorBea n/remote");

The classes needed by the client are declared using a JSP page directive (enclosed within the <%@ %> characters). Because locating the business interface and creating the enterprise bean are performed only once, this code appears in a JSP declaration (enclosed within the <%! %> characters) that contains the initialization method, jspInit, of the JSP page. A scriptlet (enclosed within the <% %> characters) retrieves the parameters from the request and converts it to a Float object. Finally, a JSP scriptlet invokes the enterprise bean?s business methods, and JSP expressions (enclosed within the <%= %> characters) insert the results into the stream of data returned to the client. The full source code for the WebClient program is given below.
<%@ page contentType="text/html; charset=UTF-8" %> <%@ page import="com.javajazzup.examples.ejb3.stateless.*, javax.naming.*"%> <%! private CalculatorRemote calculator = null; float result=0; public void jspInit() { try { InitialContext ic = new InitialContext();

calculator = (CalculatorRemote) ic.lookup("example/CalculatorBean/remot e"); System.out.println("Loaded Calculator Bean"); //CalculatorBean } catch (Exception ex) { System.out.println("Error:"+ ex.getMessage()); } } public void jspDestroy() { calculator = null; } %> <% try { String s1 = request.getParameter("num1"); String s2 = request.getParameter("num2"); String s3 = request.getParameter("group1"); System.out.println(s3); if ( s1 != null && s2 != null ) { Float num1 = new Float(s1); Float num2 = new Float(s2); if(s3.equals("add")) result=calculator.add(num1.floatValue(),num2.floatValue()); else if(s3.equals("sub")) result=calculator.subtract(num1.floatValue(),num2.floatValue()); else if(s3.equals("multi")) result=calculator.multiply(num1.floatValue(),num2.floatValue()); else result=calculator.division(num1.floatValue(),num2.floatValue()); %> <p> <b>The result is:</b> <%= result %> <p> <% } }// end of try catch (Exception e) { e.printStackTrace (); //result = "Not valid"; }

%>

Note: The Application Server automatically compiles web clients that are JSP pages. If the web client were a servlet, you would have to compile it. The source code for the ?index.jsp? is given below that will actual call the client-design form.
<%@page language="java" %> <html> <head> <title>Ejb3 Stateless Tutorial</title> </head>

<body bgcolor="#FFFFCC"> <p align="center"><font size="6" color="#800000"><b>Welcome to <br> Ejb3-Jboss 4.2.0 Tutorial</b></font> Click <a href="ejb3/form.jsp">Calculator Example</a> to execute Calculator<br></p> </body> </html> III. Deploy example onto the server To deploy the created example application we are going to use Jboss 4.2.0 Application Server about which you have read in the previous section of this Javajazzup issue. So you first need to download the following tools to deploy this application. (i) JDK 1.5 or Higher apache-ant-1.7.0 JBoss 4.2.0 Make a directory structure. You can Click here to extract the readymade directory structure according to this tutorial.

Do the following steps to deploy the example application:

(ii) Create the essential deployment descriptor .xml files.

build.xml
<?xml version="1.0"?> <project name="Jboss Tutorials" default="all" basedir=".">

<target name="init"> <!-- Define --> <property name="dirs.base" value="${basedir}"/> <property name="classdir" value="$ {dirs.base}/build/classes"/> <property name="src" value="${dirs.base}/src"/> <property name="web" value="${dirs.base}/web"/> <property name="deploymentdescription" value="$

{dirs.base}/deploymentdescriptors"/> <property name="warFile" value="example.war"/> <property name="earFile" value="example.ear"/> <property name="jarFile" value="example.jar"/> <property name="earDir" value="$ {dirs.base}/build/ear"/> <property name="warDir" value="${dirs.base}/build/war"/> <property name="jarDir" value="${dirs.base}/build/jar"/> <!-- classpath for Project --> <path id="library.classpath"> <pathelement path ="libext/servletapi.jar"/> <pathelement path ="libext/ejb3persistence.jar"/> {classpath}"/> <pathelement path ="libext/javaee.jar"/> <pathelement path ="$ </path>

<!-- Create Web-inf and classes directories --> <mkdir dir="${warDir}/WEB-INF"/> <mkdir dir="${warDir}/WEB-INF/classes"/> <!-- Create Meta-inf and classes directories --> <mkdir dir="${earDir}/META-INF"/> <mkdir dir="${jarDir}/META-INF"/> <mkdir dir="${classdir}"/> </target> <!-- Main target --> <target name="all" depends="init,build,buildWar,buildJar,buildEar"/> <!-- Compile Java Files and store in /build/src directory --> <target name="build" > <javac srcdir="${src}" destdir="${classdir}" debug="true" includes="**/*.java" > <classpath refid="library.classpath"/> </javac> </target> <!-- Create the web archive File --> <target name="buildWar" depends="init"> <copy todir="${warDir}/WEB-INF/classes"> <fileset dir="${classdir}" includes="**/*.class" /> </copy> <copy todir="${warDir}/WEB-INF"> <fileset dir="${deploymentdescription}/web/" includes="web.xml" /> </copy> <copy todir="${warDir}">

<fileset dir="${web}" includes="**/*.*" /> </copy> <!-- Create war file and place in ear directory --> <jar jarfile="${earDir}/${warFile}" basedir="${warDir}" /> </target> <!-- Create the jar File --> <target name="buildJar" depends="init"> <copy todir="${jarDir}"> <fileset dir="${classdir}" includes="**/*.class" /> </copy> <copy todir="${jarDir}/META-INF"> <fileset dir="${deploymentdescription}/jar/" includes="ejb-jar.xml,weblogic-cmp-rdbms-jar.xml,weblogicejb-jar.xml" /> </copy> <!-- Create jar file and place in ear directory --> <jar jarfile="${earDir}/${jarFile}" basedir="${jarDir}" /> </target> <!-- Create the ear File --> <target name="buildEar" depends="init"> <copy todir="${earDir}/META-INF"> <fileset dir="${deploymentdescription}/ear" includes="application.xml" /> </copy> <!-- Create ear file and place in ear directory --> <jar jarfile="../${earFile}" basedir="${earDir}" /> <copy todir="C:/jboss-4.2.0.GA/server/default/deploy/"> <fileset dir="../" includes="${earFile}" />
</copy> </target> </project>

Put this file in the base (stateless\code)directory. Application.xml

<?xml version="1.0" encoding="UTF-8"?>

<application xmlns="http://java.sun.com/xml/ns/javaee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" version="5" xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/application_5.xsd"> <display-name>Stateless Session Bean Example</display-name> <module>

<web> <web-uri>example.war</web-uri> <context-root>/example</context-root> </web> </module> <module> <ejb>example.jar</ejb> </module> </application> Put this file in the Stateless\code\deploymentdescriptors\ear directory. web.xml
<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN" "http://java.sun.com/dtd/webapp_2_3.dtd"> <web-app >
</web-app>

Put this file in the Stateless\code\deploymentdescriptors\web directory. Put all .jsp files in the Stateless\code\web directory. Put all .java files in the Stateless\code\src directory. (iii) Start command prompt, and go to the Stateless\code directory. Then type the command as: C:\Stateless\code>ant build.xml The Ant tool will deploy the example.ear file to the jboss-4.2.0.GA\server\default\deploy directory. V. Running the example Web Client Open the web browser and type the following URL to run the application: http://localhost:8080/example

Click at the given link as Calculator Example:

Give values to the textbox and choose the desire option button as Addition then clicks the Submit button to get the result.

The result is: 9.0

In this part of Enterprise Session Beans, you will learn how to develop, deploy, and run a simple Java EE application named account using stateful session bean.

Stateful Session Bean Example

In this part of Enterprise Session Beans, you will learn how to develop, deploy, and run a simple Java EE application named account using stateful session bean. The purpose of account is to performs two transaction operations (deposit and withdraw) for the customer. The account application consists of an enterprise bean, which performs the transactions, and two types of clients: an application client and a web client. here are following steps that you have to follow to develop a account JEE application. 1. Create the enterprise bean: AccountBean 2. Create the application client: AccountCustomer 3. Deploy account onto the server. 4. Run the application client. I. Creating the enterprise bean: The enterprise bean in our example is a statelful session bean called AccountBean. The account session bean represents an account information in an online customer account. The bean?s customer can deposit to or withdraw the amount from his account. To manage account, you need the following code: Remote business interface (Account) Session bean class (AccountBean)

The Business Interface:

The Account business interface is a plain Java interface that defines all the business methods implemented in the bean class. If the bean class implements a single interface, that interface is assumed to the business interface. The business interface is a local interface unless it is annotated with the javax.ejb.Remote annotation. The bean class may also implement more than one interface. If the bean class implements more than one interface, the business interfaces must be specified by decorating the bean class with @Local or @Remote. The source code for the Account business interface is given below.
package ejbExample.stateful; import javax.ejb.Remote; @Remote public interface Account { public float deposit(float amount); public float withdraw(float amount); @Remove public void remove(); }

Coding the Session Bean Class: The session bean class for this example is called AccountBean. This class implements the two business methods (deposit and withdraw). The AccountBean class must meet these requirements: The class is annotated @Stateful. The class implements the business methods defined in the business interface.

The source code for the AccountBean class is given below.

package ejbExample.stateful; import import import import javax.ejb.Stateful; javax.ejb.Remote; javax.ejb.Remove; javax.ejb.*;

@Stateful(name="AccountBean") @Remote(AccountRemote.class) public class AccountBean implements AccountRemote { float balance = 0; public float deposit(float amount){ balance += amount; return balance; } public float withdraw(float amount){ balance -= amount;

return balance; } @Remove public void remove() { balance = 0; } }

The Remove Method

Business methods annotated with javax.ejb.Remove in the stateful session bean class can be invoked by enterprise bean client to remove the bean instance. The container will remove the enterprise bean after a @Remove method completes, either normally or abnormally. Thus, we can retain the bean's state invoked by the client until we call the annotated @Remove method. In AccountBean , the remove method is a @Remove method shown as:
@Remove public void remove() { balance = 0; }

Stateful session beans also may: Implement any optional life cycle callback methods, annotated @PostConstruct, @PreDestroy, @PostActivate, and @PrePassivate. Implement optional business method annotated @Remote.

Life-Cycle Callback Methods: Methods in the bean class may be declared as a life-cycle callback method by annotating the method with the following annotations:
javax.annotation.PostConstruct javax.annotation.PreDestroy javax.ejb.PostActivate javax.ejb.PrePassivate

Life-cycle callback methods must return void and have no parameters. Lets understands these callback annotated methods shown in the table given below:
Method Description Invoked by the container on newly constructed bean instances before the first @PostConstr business method is invoked on the enterprise uct bean and after all dependency injection has completed. @PreDestroyInvoked, when the bean is about to be destoryed by EJB container before removing

the enterprise bean instance and after any method annotated @Remove has completed. Invoked by the container after the container @PostActiva moves the bean from secondary storage to te active status. Invoked by the container before the container passivates the enterprise bean, i.e. the @PrePassiva container temporarily removes the bean from te the environment and saves it to secondary storage.

II. Coding the account Web Client The application client source code is in the WebClient.jsp file That illustrates the basic tasks performed by the client of an enterprise bean: Creating an enterprise bean instance Invoking a business method

The full source code for the WebClient.jsp program is given below.
<%@page language="java" %> <%@ page contentType="text/html; charset=UTF-8" %> <%@ page import="com.javajazzup.examples.ejb3.stateful.*, javax.naming.*"%> <%! public AccountRemote account = null; float bal=0; public void jspInit() { try { InitialContext ic = new InitialContext(); account = (AccountRemote) ic.lookup("example/AccountBean/remote"); System.out.println("Loaded Account Bean"); } catch (Exception ex) { System.out.println("Error:"+ ex.getMessage()); } } public void jspDestroy() { account = null; } %> <% try {

String s1 = request.getParameter("amt"); String s2 = request.getParameter("group1"); if ( s1 != null) { Float amt = new Float(s1); if(s2.equals("dep")) bal=account.deposit(amt.floatValue()); else if(s2.equals("with")) bal=account.withdraw(amt.floatValue()); else %> <p>Please select your choice</p> <% } else %> <br>Please enter the amount<br> <p> The Transaction is complete<br> <b>Your Current Balance is:</b> <%= bal%> <p> <% }// end of try catch (Exception e) { e.printStackTrace (); } %>

The source code for the ?form.jsp? is given below.

<html> <head> <title>Bank Account</title> </head> <body> <h1><p align="center"><font size="6" color="#800000">Bank Transaction Request Form</h1> <hr><br> <table bgcolor="#FFFFCC" align="center"> <form action="WebClient.jsp" method="POST"> <tr><td></tr></td> <tr><td>Enter the amount in rupees:

<input type="text" name="amt" size="10"></tr></td> <br> <tr><td><b>Select your choice:</b></tr></td> <tr><td><input type="radio" name="group1" value ="dep">Deposit</tr></td> <tr><td><input type="radio" name="group1" value ="with">Withdraw<br></tr></td> <tr><td> <input type="submit" value="Transmit"> <input type="reset" value="Reset"></tr></td> <tr><td></tr></td> </form> </table> </body> </html>

The source code for the ?index.jsp? is given below that will actual call the client-design form.
<%@page language="java" %> <html> <head> <title>Ejb3 Stateful Tutorial</title> </head> <body bgcolor="#FFFFCC"> <p align="center"><font size="6" color="#800000"><b>Welcome to <br> Ejb3-Jboss 4.2.0 Tutorial</b></font> Click <a href="ejb3/form.jsp">Bank Transaction Example</a> to execute Bank Bean<br></p> </body> </html>

III. Deploy account onto the server IV. Running the account Application Client