Weblogic Authors: Yeshim Deniz, Elizabeth White, Michael Meiner, Michael Bushong, Avi Rosenthal

Related Topics: Weblogic

Weblogic: Article

Enhanced Component-Based Development

Enhanced Component-Based Development

Component-based development (CBD) has been around for years. Anyone who has been a developer for any length of time has no doubt leveraged some form of reuse in an application.

It may have been as simple as using a Swing component on the form of a client application. As with many areas of technology, software development and the evolution of developer tools is marked not so much by huge, dramatic leaps forward, but rather by constant innovation and improvement. When Sun Microsystems first introduced the Enterprise JavaBean (EJB) specification in 1997, no one thought that managing persistence would be such a big deal. But a big deal it was. Sun listened, and introduced Container-Managed Persistence (CMP) in the EJB 2.0 specification.

More recently, BEA has listened to its customers and provided an integrated development environment for the WebLogic platform that goes a long way toward facilitating effective CBD: BEA WebLogic Workshop. Over the course of this article, I'm going to talk about some of the challenges you face when utilizing components in Enterprise Java development and how the process can be simplified by utilizing the BEA control framework.

The time to think about how to leverage reuse in your application is at the project-planning phase. As with most aspects of software development, proper planning is essential to success. Once the program requirements are established, the first thing you should do is look in your repository and identify component candidates that can possibly be leveraged. In addition to providing the required functionality, the component must also meet the technical requirements of your application. As you go through the planning stages, be prepared with the answers to some very specific questions: Is the application intended to be Web based? Will a JavaServer Pages application in conjunction with servlets be adequate, or should you also include Web services for scalability and cross-platform flexibility? Are you building a distributed, thin-client app? Will this need the scalability and/or ease of deployment/updating provided by EJBs?

Assuming that your component repository is well documented, you should have no trouble identifying which components will be useful once these questions are answered and the program requirements are established. In many cases, the amount of "glue code" needed to integrate the component into the new project will be minimal. In other cases, there may be a fair amount of work involved. If that work estimate exceeds the amount of time it took to create the component originally, you won't see any reuse cost avoidance and you'll need to either look for another component or create one from scratch.

Another part of the planning process is determining what development environment you will use to create the individual pieces of your application. You have some flexibility here. For instance, when building an n-tier distributed app, you will probably use an IDE such as JBuilder for the client portion. You might use JBuilder for the server-side development as well, or you might decide to go with WebLogic Workshop.

WebLogic Workshop and the BEA Control Framework
BEA WebLogic Server is a powerful platform for Enterprise Java development. BEA WebLogic Workshop is tightly integrated to provide an integrated development and testing environment for Web services (and, soon, Web applications) for the WebLogic platform. As such, it is important for you to consider the added benefits that the BEA control framework provides.

For example, let's assume that as a result of your project planning, you have identified several EJB components that you wish to leverage in your new project. By taking advantage of WebLogic Workshop and the BEA control framework, as well as the inherent flexibility of the J2EE platform, you can create a distributed, scalable, back-end system that supports a variety of client deployments, including a Web application, a thin-client Java application, cross-platform deployment, and more!

To demonstrate this, I'm going to take you through some sample applications that utilize EJBs to provide back-end business logic. We'll also look at how the BEA control framework simplifies the process of integrating these EJBs into our Web services and Web applications.

Note: The sample applications referenced here come packaged with WebLogic Workshop. This allows me to focus on the component-specific aspects within the broader context of a JWS project and enables you to reference the sample projects in your own Workshop environment and experience a working demo.

Entity Beans
Entity beans represent data. They are usually mapped either to records of a relational database or to objects of an object-oriented database. They are transactional in that changes to their state typically occur within the context of a transaction. An instance of an entity bean may be referenced by multiple clients. The container - in this case WebLogic Server - is responsible for ensuring that the data in the bean and the corresponding database are synchronized. Figure 1 shows the sample project, "AccountEJBClient.jws", loaded into WebLogic Workshop. As you can see, Workshop has wrapped the bean as an EJB control and has implemented control interfaces that map to corresponding EJB methods.

If we were using this bean in another environment, we would have to go through a bit of a process in order to use it. First, we would have to look up the EJB in the JNDI registry and obtain the home interface. Next, we would need to obtain an instance of the EJB. Finally, we could invoke its methods. While this is by no means a difficult or complicated process, utilizing the control framework makes instantiating and accessing the bean even simpler. All we have to do is add a new EJB control (see Figure 2), point to the EJB (see Figure 3), and we're done. As you can see, once you've browsed to the EJB, Workshop automatically finds the home and remote interfaces. It takes every method of the bean and creates a corresponding control interface. It creates a corresponding control file (.CTRL) for each control created. Listing 1 shows the control file for this EJB control.

Note: Some controls can be modified by editing the CTRL file. Do not edit an EJB's CTRL file. It is created by Workshop based upon information it obtains from the EJB's code.

Now that the control has been created, it automatically handles the J2EE plumbing such as instantiating and destroying the bean, accessing the methods, and the like. Please remember that you must have a local copy of the EJB's JAR file in the WEB-INF\lib directory of your Workshop project in order for Workshop to discover the EJB's home and remote interfaces.

Listing 2 shows how WebLogic Workshop accesses the EJB and is the code for the createNewAccount operation. It calls the Create method of the EJB control (which wraps the J2EE interfaces of the EJB's Create method). As you can see, Workshop has done the work of specifying the method parameters as well as putting in exception handling. Since this is a simple "Web Service method to EJB method" mapping, there is little else to do (assuming you trust the functionality of the EJB). However, you can add custom validation code here if you wish.

Session Beans
Session beans represent particular business process steps. They capture the interaction or conversation between the user and the system. Session beans come in two flavors: stateful and stateless. Stateful session beans maintain state across multiple remote method invocations by a client on the same client-proxy of the session bean. Every method invocation by the client is routed to the same session bean instance on the server. These are useful when you need to carry out a long conversation with the server and you need the server object to save the conversational state. An example of a stateful session bean is an online shopping cart, where a client might use remote methods to add, remove, or modify the products in the shopping cart.

Stateless session beans do not maintain any state that the client can depend on between multiple remote method invocations. These are useful for situations where the duration of the method execution constitutes a complete unit of work from the client's perspective. For an example of a Stateless Session Bean, open the 'TraderEJBClient.jws' sample project in WebLogic Workshop. As you can see from the JWS operations (see Figure 4), this component has only two methods: Buy and Sell. The EJB control (which wraps the interfaces of the EJB itself) actually has a third interface: Create. In fact, every session and entity EJB contains this method. This is how the instance of the bean is actually created. When dealing with entity beans, this method must be explicitly called - since creating an instance of an entity bean actually creates a new row in the corresponding datasource. However, with WebLogic Workshop it is not necessary to fire off the Create method of session beans. The BEA control framework automatically creates an instance of the bean when any of the methods are called. Even if you do explicitly call the Create method, you might not get a new instance. WebLogic Server may simply return an existing instance of the bean.

Since this is a fine-grained component, I have included both the Buy and Sell method calls in Listing 3. You'll notice that there is very little (if any) validation going on here. One glaring weakness is the lack of any validation that the user actually owns a sufficient quantity of shares to cover the sale. This validation is best added into the client portion of your application, or as part of a larger Web service - one that integrates an entity bean for account management and a stateful session bean to handle an extended conversation with the server (perhaps for transacting multiple stock sales). You want this validation complete before you even instantiate this bean.

Message-Driven Beans
Message-driven Beans (MDBs) enable the development of asynchronous applications. They essentially sit on the server and wait for Java Message Service (JMS) messages. They are anonymous in that no client may hold a reference to an MDB - only the EJB container may access the bean directly. They have neither a home nor a remote interface. As such, they cannot be used inside WebLogic Workshop. There is, however, an alternative. The BEA control framework includes a JMS control that you can add to your Workshop project. It can then listen for callbacks. Figure 5 shows a JWS project for credit reporting that uses a JMS control to receive credit information from the queue. Listing 4 shows the receiveMessage callback handler that processes the callback. This provides the same basic functionality of an MDB from within the Workshop environment.

Mission-critical applications that depend on tried-and-tested code benefit greatly from component reuse. WebLogic Server - in conjunction with WebLogic Workshop - can make the integration of these components a breeze.

Comments (0)

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.

IoT & Smart Cities Stories
Contextual Analytics of various threat data provides a deeper understanding of a given threat and enables identification of unknown threat vectors. In his session at @ThingsExpo, David Dufour, Head of Security Architecture, IoT, Webroot, Inc., discussed how through the use of Big Data analytics and deep data correlation across different threat types, it is possible to gain a better understanding of where, how and to what level of danger a malicious actor poses to an organization, and to determin...
The hierarchical architecture that distributes "compute" within the network specially at the edge can enable new services by harnessing emerging technologies. But Edge-Compute comes at increased cost that needs to be managed and potentially augmented by creative architecture solutions as there will always a catching-up with the capacity demands. Processing power in smartphones has enhanced YoY and there is increasingly spare compute capacity that can be potentially pooled. Uber has successfully ...
The deluge of IoT sensor data collected from connected devices and the powerful AI required to make that data actionable are giving rise to a hybrid ecosystem in which cloud, on-prem and edge processes become interweaved. Attendees will learn how emerging composable infrastructure solutions deliver the adaptive architecture needed to manage this new data reality. Machine learning algorithms can better anticipate data storms and automate resources to support surges, including fully scalable GPU-c...
We are seeing a major migration of enterprises applications to the cloud. As cloud and business use of real time applications accelerate, legacy networks are no longer able to architecturally support cloud adoption and deliver the performance and security required by highly distributed enterprises. These outdated solutions have become more costly and complicated to implement, install, manage, and maintain.SD-WAN offers unlimited capabilities for accessing the benefits of the cloud and Internet. ...
Dion Hinchcliffe is an internationally recognized digital expert, bestselling book author, frequent keynote speaker, analyst, futurist, and transformation expert based in Washington, DC. He is currently Chief Strategy Officer at the industry-leading digital strategy and online community solutions firm, 7Summits.
As IoT continues to increase momentum, so does the associated risk. Secure Device Lifecycle Management (DLM) is ranked as one of the most important technology areas of IoT. Driving this trend is the realization that secure support for IoT devices provides companies the ability to deliver high-quality, reliable, secure offerings faster, create new revenue streams, and reduce support costs, all while building a competitive advantage in their markets. In this session, we will use customer use cases...
Machine learning has taken residence at our cities' cores and now we can finally have "smart cities." Cities are a collection of buildings made to provide the structure and safety necessary for people to function, create and survive. Buildings are a pool of ever-changing performance data from large automated systems such as heating and cooling to the people that live and work within them. Through machine learning, buildings can optimize performance, reduce costs, and improve occupant comfort by ...
René Bostic is the Technical VP of the IBM Cloud Unit in North America. Enjoying her career with IBM during the modern millennial technological era, she is an expert in cloud computing, DevOps and emerging cloud technologies such as Blockchain. Her strengths and core competencies include a proven record of accomplishments in consensus building at all levels to assess, plan, and implement enterprise and cloud computing solutions. René is a member of the Society of Women Engineers (SWE) and a m...
With 10 simultaneous tracks, keynotes, general sessions and targeted breakout classes, @CloudEXPO and DXWorldEXPO are two of the most important technology events of the year. Since its launch over eight years ago, @CloudEXPO and DXWorldEXPO have presented a rock star faculty as well as showcased hundreds of sponsors and exhibitors! In this blog post, we provide 7 tips on how, as part of our world-class faculty, you can deliver one of the most popular sessions at our events. But before reading...
Poor data quality and analytics drive down business value. In fact, Gartner estimated that the average financial impact of poor data quality on organizations is $9.7 million per year. But bad data is much more than a cost center. By eroding trust in information, analytics and the business decisions based on these, it is a serious impediment to digital transformation.