Introduction to Java Services Orchestration for Actions
Tutorial Details:
Summary
Thus far, Web application development has focused on encapsulating business logic as services. In this article, Masayuki Otoshi proposes a separation of business flow as well by applying the concept of describing processes in XML-based documents like business-process-management/workflow products, but here he looks at lower granularity in actions.
In developing Web applications, we often see that business flow and logic are implemented together in actions, such as backing-beans in JavaServer Faces (JSF) and action classes in Struts.
Business process management (BPM) standards, e.g., Business Process Modeling Notation (BPMN) and Business Process Execution Language (BPEL), provide a way to separate business flow by describing it with XML-based documents. This approach also provides the benefit of being able to design applications based on service-oriented architecture (SOA). However, this approach doesn't work well with "actions" in Web applications.
Sample action in JSF
Let's take a look at some sample action code in a Web application developed using JSF. Our example is a simplified model search application, which responds with model information corresponding to the model ID the user entered.
In the search form JSP (JavaServer Pages) page, there is a text box and a Submit button for entering the model ID. The JSP page invokes the showModel() method in a backing bean named ModelBean
Read
Tutorial at: Click here to view the tutorial
Rate Tutorial: Separate business flow from actions
View Tutorial: Separate business flow from actions
Related
Tutorials:
 One, two, three,
or n tiers? - JavaWorld January 2000
One, two, three,
or n tiers? - JavaWorld January 2000
|
Building a Java servlet framework
using reflection, Part 2 - JavaWorld February 2000
Building a Java servlet framework
using reflection, Part 2 - JavaWorld February 2000
|
Java security evolution
and concepts, Part 1: Security nuts and bolts - JavaWorld April
2000
Java security evolution
and concepts, Part 1: Security nuts and bolts - JavaWorld April
2000
|
Alternative deployment
methods, Part 3: The code - JavaWorld September
2000
Alternative deployment
methods, Part 3: The code - JavaWorld September
2000
|
Boost Struts with
Boost Struts with XSLT and XML
|
Use Web services
to integrate Web applications with
EISs
Use Web services
to integrate Web applications with
EISs
|
Customized EJB
security in JBoss
Customized EJB
security in JBoss
|
Business process
automation
made easy with
Java, Part 1
Business process
automation
made easy with
Java, Part 1
|
Transform data into Web applications with Cocoon
Transform data into Web applications with Cocoon
|
Protect Web
application
control flow
Protect Web
application
control flow
|
confusing
title
confusing
title
|
JSP 2.0: The New Deal, Part 4
JSP 2.0: The New Deal, Part 4
In this final part of the "JSP 2.0: The New Deal" series, we look at two new features that make it much easier to develop custom tag libraries: tag files and the new simplified tag-handler Java API.
|
Creating JSF Custom Components
Creating JSF Custom Components
This article illustrates how to build custom components for use in web applications based on JavaServer Faces (JSF). While JSF comes with a standard set of components, one of the most-publicized features is the easy additio
|
Handling Events in JavaServer Faces, Part 1
In this excerpt from the book, author Hans Bergsten looks at the JSF event model, using examples to help explain what\'s going on "under the hood."
|
Java validation with dynamic proxies
Decouple validation processes from your business object implementations.
|
Smokescreen Introduction
Smokescreen is a Java obfuscator. Aside from being able to change symbolic names, it can also modify the bytecode instructions in methods thereby obfuscating control flow. This makes the resulting obfuscated classes much more difficult to decompile.
|
Smokescreen 3.4 has been released
Smokescreen is a Java obfuscator. Aside from being able to change symbolic names, it can also modify the bytecode instructions in methods thereby obfuscating control flow. This makes the resulting obfuscated classes much more difficult to decompile.
|
The On Demand Operating Environment
The On Demand Operating Environment is based upon the concepts of Service Oriented Architecture (SOA). SOA views every application or resource as a service implementing a specific, identifiable set of (business) functions. In addition to the business...
|
Getting Started with Java Message Service (JMS)
The Java Message Service (JMS) is designed to allow Java applications to use enterprise messaging systems. It makes it easy to develop enterprise applications that asynchronously send and receive business data and events. Learn how to implement it for you
|
Using Taglib in JSP. A brief introduction to taglibs and taglibs programing.
Using Taglib in JSP. A brief introduction to taglibs and taglibs programing.
JSP TAG LIBRARIES
JSP Tag Libraries :
JSP’s offer a unique feature of “Tag Libraries”. Simply put, these are custom defined JSP tags. They are basically meant for
|
|
|
|
