CRUD Operation using JSF, web services and OJB

This article explains the use case of adding, updating, searching and deleting using JSF, Web Services and OJB in WebSphere Integration Developer version 6.1. The article discusses the steps in developing each layer including the integration among these layers.


Kamesh Pandrangi, System Engineer, IBM  

PandrangiKamesh Pandrangi has been working at IBM for over 4 years. His expertise include development of J2EE applications and reusable assets for SOA.He has delivered assets for the Enrollment to File of Healthcare CBS. His Area of Interests are software modeling, learning upcoming technologies and exploring new products in SOA.

30 October 2009

Also available in Japanese


With the introduction of web services as a place holder for core business logic based on SOA platform enabled the enterprise application development in an independent layer structure thus making it easy for development and maintenance as well.

In this article we will discuss the development of each layer and the interaction among layers; resulting in an end-to-end enterprise solution. CRUD operations being the basic operations for any kind of enterprise business, addressing these areas gives an overview for the designing and developing the solutions based on SOA. To answer the technical challenges and show the capabilities JSF is used for developing the User Interface layer and OJB for handling the data at data layer.

Figure 1. Web service
web services

Java Server interface

The user interface (UI) layer is developed using Java Server Faces Technology. It includes:

  • A set of APIs for representing the UI components and managing their state, handling events and input validation, converting values, defining page navigation, and supporting internationalization and accessibility
  • A default set of UI components
  • Two JavaServer Pages (JSP) custom tag libraries for expressing a JavaServer Faces interface within a JSP page
  • A server-side event model
  • State management
  • Managed Beans (JavaBeans created with dependency injection)
  • Unified Expression Language for both JSP 2.0 and JSF 1.2

Creating a JSF project is similar to the creating a normal web project in WebSphere Integration Developer (WID) 6.1. The user friendly features of WID enable the user to easily create Web projects. Below, we begin by creating a Dynamic Web project. The following steps begins the process of building the JSF project in WID 6.1.

  • Right-click on Project Explorer > Select New > Select Dynamic Web Project
  • Specify the Project name and EAR name
  • Check the required Project Facet like JSTL, Basic Facet Support that enable us to use the features of built in functionality
  • Specify the Context Root, Content Directory & Java Source Directory
  • Create a new JSF page by Right clicking on Web Content > New > JSP
  • Specify the JSF page name
Figure 2. Importing JSP templates
Importing JSP templates

Open the page in design view and add the required components from the Enhanced Faces Components. These enhanced Faces Components provide a rich a set of widgets that are normally used in developing applications such as a drop down list, selection list, data table, and panels. The biggest advantage with JSF is addressing the many user interface components in basic form and connecting them with the relevant operations in the JavaBean. To make a good look and feel we will build the components in a table to view the alignment and position of fields in a consumable way.

  • Click on the HTML Tags > Select Table > Specify the number of rows and columns
  • Add the required labels for the form fields
  • Click on Enhanced Faces Components > Select Input > Drag into required cell
  • Repeat the process to add other components
Figure 3. Properties of JSF components
Properties of JSF components

Dpecify the properties of a component by clicking on the Properties tab.

Once we are finish with designing the page using the widgets and other components. We then look into the next part of mapping the components to the relevant properties at the JavaBean. Within the JSF we call it as managed bean that holds the properties and provide operations on them, the following steps describe how to start up with the managed bean.

  • Create a managed bean with required properties
  • Select the property > right-click > Generate Getters & Setters
  • Create a method and specify the required operation (either the actual business logic or Service Invocation), Figure 4 shows how we work with managed beans.
Figure 4. Managed Bean properties and operations
Managed Bean Properties and Operations
Figure 5. Page data
Page data

In Page Data right click on Use Bean > New > JavaBean.

Figure 6. Data component
Data component

Selection of the faces managed bean

Once the managed bean is created with the required properties and method innovations, we specify the name for the managed bean with its corresponding class. Depending on the functionality and usage of the class we make this bean as reusable by specifying its scope. These are reflected in faces-config.xml.

This new bean definition is completed within th bottom-left panel called Page Data where we select the Faces Managed Bean, once you refresh the Faces Managed Beans in Page Data, you can view the bean with its available variables and methods. Using Websphere Integration Developer directly map the bean properties to the fields that are designed and developed in JSF page. Figure 7 shows the drag and drop functionality provided in WID.

Figure 7. Drag & Drop bean properties
Drag Drop bean Properties

Similarly you can also map the properties and operations for other operations of Retrieve, Update and Delete. Once the four operations are complete deploy the EAR onto the server and test it using the test clients that will push the data from User Interface to the next layer.

  • Map the variables to the corresponding field in Design View
  • Map the method to be triggered on Submitting the form to the Submit button

Using web services

Web services form an interoperable layer that connects the user interface and database layer.

Figure 8. Overview of web services
Overview of web services

Services are defined using six major elements:

  1. Types, which provides data type definitions used to describe the messages exchanged.
  2. Message, which represents an abstract definition of the data being transmitted. A message consists of logical parts, each of which is associated with a definition within some type system.
  3. PortType, which is a set of abstract operations. Each operation refers to an input message and output messages.
  4. Binding, which specifies concrete protocol and data format specifications for the operations and messages defined by a particular portType.
  5. Port, which specifies an address for a binding, thus defining a single communication endpoint.
  6. Service, which is used to aggregate a set of related ports.

The web service creates an interoperable layer that connects the user interace and the database layer. This enables us to store the business logic and define rules as and when and re-deploy only this layer whenever changes come. It provides us the flexible way to upgrade the UI and back end layer without disturbing core business logic.

We follow three major steps in creating a web service here:

  1. Creating a library that stores the Data Objects and WSDL's
  2. A Web project to store the generated java skeletons
  3. A java project to store the generated client

Creating the library

The creation of a library and storing the created WSDL helps us to share the library with other projects and provides a common place for managing them. This library is also used to store the data objects that are used across the project. So at any point of time any updates on these data objects can be made at a single place to avoid the conflict in other projects.

Depending on the type of operations and the data used in the project the data objects are defined. In the day to day business operations the data is wrapped in the meaningful form of objects that are transferred in XML format. We have many XML parsers that will wrap and unwrap these complex objects and serve the business need. Since these data objects are defined in a common place like library and imported by interface, they can be updated as an when required without changing the actual wsdl definition.

The following steps provides guidance with the creation of library and Data objects:

  • Select Library and click Next
  • Create a new XSD by Right clicking on Web Content > New > Other > XML > XMLSchema
  • Right click on newly created XSD and open with Business Object Editor as shown in Figure 9
  • Specify the name and type for the element in Properties Tab

At this point we can group the object of objects thus creating a complex object as a whole, where each object can contain the primitive data types like integer, string or a Boolean value. The basic structure of a complex object can be depicted in figures 9 and 10.

Figure 9. Working with the Business Object Editor
Working with Business Object Editor
Figure 10. Structure of Complex Business Object
Structure of Complex Business Object

Once we are ready with the data objects, we can create a wsdl that takes these data objects as inputs and outputs depending on the operation type. To use these data objects we need to import them to our wsdl specifying the corresponding namespace.

Generating the JavaBean

The WSDL's created earlier define the operations performed with input and output parameters. The actual core business logic is defined by implementing those operations, this can be achieved by generating the Java Bean shell. Figure 11 demonstrate how to create the Java Bean shell.

Figure 11. Structure of Complex Business Object
Structure of Complex Business Object

Right click on WSDL > Select Web Services > Generate Java bean skeleton

Figure 12. Specify Service Project Settings
Specify Service Project Settings

Specify the Service Project Name with its project type and EAR name.

Generating client

To check the implemented classes functionality we generate client that actually make a call to the web service and confirm us that everything is fine. In real time we actually give the wsdl to the user from which they generate the client and invoke for the required functionality. Figure 13 shows how to create the client.

Figure 13. Generating the Client
Generating the Client

Right click on WSDL > Select web services > Generate Client

Figure 14. Specify Client Project Settings
Specify Client Project Settings

Click on Client Project > Specify the Client Project Name

ObJectRelationalBridge (OJB)

Data being the major component in any project should be manipulated and stored in a right way at right time. Delay in response time or dirty read/write will degrade the performance of the system and keeping the system in an inconsistent state as a whole. In the current tutorial the DB layer sits at the end storing the data that is passed through UI layer and service layer.

With the introduction of ORM tools the data manipulation and maintenance became easy that can be directly mapped with the java, OJB is one among them that is designed developed by Apache. It allows persistence for java objects against relational databases.

The following are some key features of OJB:

  • Provides flexibility through support to multiple persistence APIs
  • The applications that are designed and developed using OJB are scalable for future enhancements.
  • It support JNDI lookups and Bean Managed Persistence
  • The XML based ORM helps to manipulate during run-time
  • It provides a flexible configuration and plug-in mechanism that allows to select from set of predefined components.
  • The open source feature with 100% pure Java orientation facilitates rapid development.

With the completion of the user inteface layer and services layer we move into the database layer which actually saves the data into the database. The annotations and xml configuration features provided by OJB enables us to map the table columns with the bean properties directly thus making the data manipulations easy. The built-in methods in OJB help us to store ,update and delete the data in a object model.

Figure 15. Creating New Java Project
Creating New Java Project

To achieve this we create a Java Project with two main packages that store DAO’s and Domain classes. Following the java naming conventions create the packages with appropriate names. The Domain package stores the classes that contain doclets mapping the properties to that of columns in the specific table, while the DAO package contains the real operational methods that stores the domain object. Import the required Jars into the lib folder. This include the necessary jars for the database support, in this article we use DB2 as database and import them accordingly.

Figure 16. Configuring the repository_database.xml
Configuring the repository_database.xml

Once we are done with the basic packaging structure and importing of dependent jar files we moved ahead with configuring the XML files. The files are stored in the config folder, the main config file include repository_database.xml that is used to configure the database name and other credentials. The next file we deal is the build.xml that actually map the location of domain objects and classpath from where required jars are loaded. It also specifies the target location for files project-schema.xml and repository_user.xml. These two files will be generated and placed in config folder once we run the build.xml file. Figure 17 shows the typical build.xml file.

Figure 17. Configuring the build.xml
Configuring the build.xml

Integrating the user interface with services

Now we are ready with three individual layers and need to integrate them to make an end-to-end flow. Firstly we integrate the user interface with web services. Since the user interface is a dynamic Web project, adding the service client jar makes the operations defined in web service to be available to the user interface layer. This can be achieved in the following way, described below.

Figure 18. Adding web service client to UI
Adding web service client to UI

Right Click on UI Project > Properties > J2EE Module Dependencies > Check the Client JAR

Invoke the service using service locator and locate the endpoint with appropriate port type. If the server is listening in another port, we need to change accordingly. Depending on the object type at user interface layer we map them to objects that are defined at service layer. Figure 19 shows the sample code for invoking web service from a managed bean in user interface layer.

Figure 19. Service Invocation from Managed Bean
Service Invocation from Managed Bean

Integrating the services with the database layer

The integration of services with database layer includes adding the database java project as dependency jar in web service project J2EE Module dependencies. Make certain that the required jars for the database project are already added in EAR that is generated for the web service project. Figure 20 shows adding the data project as dependency jar to the web service project.

Figure 21. Adding DB jar dependency
Adding DB jar dependency

Right Click on Web Service Project > Properties > J2EE Module Dependencies > DB JAR

Figure 21. Creating Domain and DAO objects
Creating Domain and DAO objects
  • Create the Domain and DAO Objects
  • Set the domain object using appropriate DAO


This article summarized the rapid application development on SOA platform using the services as core layer with cutting edge technologies like JSF and OJB. It focused on development of each layer and integrating with the other layers. This is an basic approach to start and visualise the SOA and identify the interopability of services that can glue any kind of technology together.



Get products and technologies



developerWorks: Sign in

Required fields are indicated with an asterisk (*).

Need an IBM ID?
Forgot your IBM ID?

Forgot your password?
Change your password

By clicking Submit, you agree to the developerWorks terms of use.


The first time you sign into developerWorks, a profile is created for you. Information in your profile (your name, country/region, and company name) is displayed to the public and will accompany any content you post, unless you opt to hide your company name. You may update your IBM account at any time.

All information submitted is secure.

Choose your display name

The first time you sign in to developerWorks, a profile is created for you, so you need to choose a display name. Your display name accompanies the content you post on developerWorks.

Please choose a display name between 3-31 characters. Your display name must be unique in the developerWorks community and should not be your email address for privacy reasons.

Required fields are indicated with an asterisk (*).

(Must be between 3 – 31 characters.)

By clicking Submit, you agree to the developerWorks terms of use.


All information submitted is secure.

Dig deeper into SOA and web services on developerWorks

Zone=SOA and web services
ArticleTitle=CRUD Operation using JSF, web services and OJB