Welcome!

Microservices Expo Authors: Liz McMillan, Flint Brenton, Jason Bloomberg, Elizabeth White, Yeshim Deniz

Related Topics: Microservices Expo

Microservices Expo: Article

Developing J2EE 1.4 Web Services on the Fly

Developing J2EE 1.4 Web Services on the Fly

As Web services technology becomes pervasive, the beta release of Java 2 Enterprise Edition (J2EE) 1.4, which focuses primarily on Web services, flags a milestone in the Web services developer community. Sun's J2EE Reference Implementation (RI) helps developers to easily understand the technology through its robust implementation of the specification. The J2EE 1.4 specification (JSR-151) adds a lot of functionality to the platform. The core theme of J2EE 1.4 circumvents Web services. It has incorporated most of the Web services-related JSRs in its specification, including JSR-109 (Implementing Enterprise Web Services), JSR-101 (Java APIs for XML-based RPC), JSR-67 (Java APIs for XML Messaging 1.0), and JSR-93 (Java API for XML Registries 1.0).

Basically, a Web service client can access J2EE applications in two ways. First, the client can access a Web service created with JAX-RPC. Second, the client can access an EJB Web service (only stateless session beans) through its Web service endpoints. The bottom line is that JAX-RPC uses a servlet to implement the Web service. This helps in exposing the existing stateless session beans as Web services.

In this article, I'll deal with the development of a Web service using the J2EE 1.4 platform. I'll use the JAX-RPC APIs that form the basis for developing J2EE 1.4 Web services on the fly.

Creating a Web Service with JAX-RPC
Remote Procedure Call (RPC) is a mechanism through which you invoke procedures (or services) from a remote client. In the Java world, we have the Java API for XML-based RPC (JAX-RPC) in which service invocation takes place through an XML-based protocol called Simple Object Access Protocol (SOAP) over HTTP transport. Since the J2EE 1.4 platform uses standard technologies such as XML, SOAP, and HTTP, it is easy for developers to create Web services that are platform independent and interoperable.

The typical life cycle of a Web service has three stages: develop the Web service, deploy the Web service, and invoke the Web service. We'll follow this life cycle in developing our Web services using J2EE 1.4. We will consider the familiar stock quote application for our illustration. A stock quote service is deployed in the server. The client invokes the service by passing a stock symbol. Here, the service and the client are developed using the JAX-RPC APIs. Figure 1 shows the interactions between the Stock quote Web service and the stock quote client. Stubs are the client-side proxies used to communicate with the service. Ties are the classes the server needs to communicate with a remote client. Stubs and ties are low-level classes that perform similar functions, i.e, stubs on the client side and ties on the server side.

 

Building and Deploying the Service
The steps that are involved in building and deploying the service are:

  1. Define the interface class for the service.
  2. Implement the interface class.
  3. Compile the classes and generate WSDL.
  4. Package the classes as an EAR file.
  5. Deploy the service.
Service Interface
Our stock quote service has one method, getQuote, which takes the symbol as the argument and returns the value of the stock symbol. The interface definition for the stock quote service is shown in Listing 1.

Service Implementation
The service implementation StockQuoteImpl implements the interface StockQuote IF. This connects to an Axis stock quote service that is running on the www. xmethods.net server. The getQuote request made to this service returns an XML document that contains the value of the stock. If you are behind a firewall, you need to specify the proxyHost and proxyPort properties in order to access the service. The implementation for the stock quote service is shown in Listing 2.

Generating the WSDL File
J2EE 1.4 provides a tool called wscompile.bat, which generates the WSDL file for the service. The Ant target generate-wsdl does this for you and runs this tool as follows:

wscompile.bat -define -d build/server -nd build/server
-classpath build/server service-config.xml

The generated WSDL file MyStock QuoteService.wsdl is shown in Listing 3. The Ant target build-service compiles the service classes and the generation of the WSDL file for the service.

Packaging the Service
To package the service, use the ant target package-service, which packages the service and its dependent files in a stockquote.ear file. This EAR file bundles the stockquote-jaxrpc.war file in it. The contents of these WAR and EAR files are:

stockquote-jaxrpc.war
META-INF/
META-INF/MANIFEST.MF
WEB-INF/
WEB-INF/classes/
WEB-INF/classes/stockquote/
MyHelloService.wsdl
WEB-INF/classes/stockquote/StockQuoteIF.class
WEB-INF/classes/stockquote/StockQuoteImpl.class
WEB-INF/mapping.xml
WEB-INF/web.xml
WEB-INF/webservices.xml

stockquote.ear
META-INF/
META-INF/MANIFEST.MF
stockquote-jaxrpc.war
META-INF/application.xml
META-INF/sun-j2ee-ri.xml

Deploying the Service
J2EE 1.4 provides a tool called deploytool.bat for deploying Web applications. The developed EAR file is deployed in the server using this tool. This can be done with the help of the Ant target deploy-service. As a precondition, you need to start the database server from the command prompt by typing

%J2EE_HOME%/bin/cloudscape.bat -start

Start the J2EE server from the command prompt by typing

%J2EE_HOME%/bin/j2ee.bat -verbose

to start the server in verbose mode. The Ant target runs the deploy tool as follows:

deploytool.bat -id stockquote-jaxrpc
-deployModule stockquote.ear

This deploys the stock quote service in the server. To verify that the service has been successfully deployed, execute the Ant target "list", which lists all the applications that are deployed on the server. You can verify the successful service deployment by typing the following URL in your browser:

http://localhost:8000/stockquote-jaxrpc/mystockquote?WSDL

If you can see the WSDL file on your browser, the service is deployed successfully.

Building and Running the Client
The steps involved in building and running the client are:

  1. Generate the stubs.
  2. Code the client class.
  3. Compile the client class.
  4. Package the classes as a JAR file.
  5. Run the client.
Generate the Stubs
Stubs are the client-side proxies for the service. J2EE 1.4 provides a tool called wscompile.bat for generating these stubs. The Ant target generate-stubs, defined in our build.xml, does this task for you. This target runs the tool as follows:

wscompile.bat -gen:client -d build/client
-classpath build/server client-config.xml

The wscompile.bat tool generates files based on the information that it reads from the MyStockQuoteService.wsdl. The -gen: client option instructs the tool to generate the client-side classes called stubs. The -d option instructs the tool in which directory the generated stubs are to be placed. The -classpath option instructs the tool where to find the input classes. The tool reads the config file "client-config.xml" which has the information about the location of the WSDL file. The client configuration file client-config. xml is shown in Listing 4.

Service Client
Once the service is defined, implemented, and deployed, it is ready for access by the clients. The client uses the generated stubs to interact with the service. This is a static client as it was created before runtime. The client takes the service endpoint as the input argument, and invokes the getQuote method by passing the symbol "HPQ". The service returns the value of the symbol to the system console. This is the real-time quote of the symbol with a delay of 20 minutes. The client for accessing the stock quote service is shown in Listing 5.

Compiling and Packaging the Client
The Client sources along with the stubs are compiled and packaged as a JAR file by the Ant targets compile-client and package-client. This generates a file - client.jar that is used in invoking the stock quote service.

Setup Instructions for Running the Web Service
Required Software:

  • Download Ant 1.5.3 from http://ant.apache.org
  • Download J2SE 1.4.1 from http://java.sun.com/j2se/1.4.1/download.html
  • Download J2EE 1.4 Beta from http://java.sun.com/j2ee/1.4/download.html#sdk

    Setting Up Environment Variables
    To run the StockQuote application, you need to set the following environment variables:

  • J2EE_HOME=C:\j2sdkee1.4
  • JAVA_HOME=C:\j2sdk1.4.1_02
  • ANT_HOME=H:\apache-ant-1.5.3
  • PATH=%JAVA_HOME%/bin;%J2EE_HOME%\bin;%ANT_HOME%\bin;%PATH%

    Invoke the Service Using the Web Service Client
    Download the source code of the developed Web service. Extract this under "J2EE_HOME\doc\samples". The "build. xml" file bundled with this application defines all of the tasks discussed above as Ant targets. Before proceeding further, you need to change the proxy-related information in the StockQuoteImpl.java class.

    As a precondition, you need to start the database and J2EE servers by using the following commands:

    %J2EE_HOME%/bin/cloudscape.bat -start
    "%J2EE_HOME%/bin/j2ee.bat -verbose

    This starts the server in verbose mode. Wait until the command window displays "J2EE server startup complete." Now you are ready to execute the Ant targets that will help you build, deploy, and invoke the Web service.

    Execute the following targets:

  • Ant build-service: Compiles the service sources.
  • Ant package-service: Packages the service classes and related files in an EAR file.
  • Ant deploy-service: Deploys the service in the server.
  • Ant list: Lists the deployed service.
  • Ant build-client: Compiles the client sources.
  • Ant package-client: Packages the client classes as a JAR file.
  • Ant run: Invokes the service. Figure 2 shows the output of the client after invoking the service. It returns the value of the symbol with a delay of 20 minutes.
  • Ant undeploy: Undeploys the service from the server.

     

    Conclusion
    Tools always ease the development of application software. With the help of robust tools, developers can spend more time designing the applications than developing the applications. The current release of the J2EE 1.4 platform provides some basic tools that ease the development of Web services. The J2EE 1.4 final release plans to have support for Web Services - Interoperability (WS-I) basic profiles. Developing and deploying Web services on the fly is a reality with the arrival of the J2EE 1.4 platform.

    References

  • J2EE 1.4 Platform Home: http://java.sun.com/j2ee/
  • J2EE 1.4 Specification: http://java.sun.com/j2ee/j2ee-1_4-pfd2-spec.pdf
  • JSR 151: www.jcp.org/en/jsr/detail?id=151
  • The J2EE Tutorial Addendum: http://java.sun.com/j2ee/1.4/docs/tutorial/index.html
  • More Stories By Arulazi Dhesiaseelan

    Arulazi Dhesiaseelan holds Master of Computer Applications degree from PSG College of Technology, India. He has been involved in designing and building Java based applications and SDK for more than three years. He was also involved in the API development of UDDI4j project hosted at http://uddi4j.org. He's working with Hewlett Packard Company (India Software Operations), Bangalore. Currently he is involved in the development of an open service framework for mobile infrastructures. He can be reached at [email protected]

    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.


    @MicroservicesExpo Stories
    All organizations that did not originate this moment have a pre-existing culture as well as legacy technology and processes that can be more or less amenable to DevOps implementation. That organizational culture is influenced by the personalities and management styles of Executive Management, the wider culture in which the organization is situated, and the personalities of key team members at all levels of the organization. This culture and entrenched interests usually throw a wrench in the work...
    Don’t go chasing waterfall … development, that is. According to a recent post by Madison Moore on Medium featuring insights from several software delivery industry leaders, waterfall is – while still popular – not the best way to win in the marketplace. With methodologies like Agile, DevOps and Continuous Delivery becoming ever more prominent over the past 15 years or so, waterfall is old news. Or, is it? Moore cites a recent study by Gartner: “According to Gartner’s IT Key Metrics Data report, ...
    Many organizations are now looking to DevOps maturity models to gauge their DevOps adoption and compare their maturity to their peers. However, as enterprise organizations rush to adopt DevOps, moving past experimentation to embrace it at scale, they are in danger of falling into the trap that they have fallen into time and time again. Unfortunately, we've seen this movie before, and we know how it ends: badly.
    In his session at Cloud Expo, Alan Winters, U.S. Head of Business Development at MobiDev, presented a success story of an entrepreneur who has both suffered through and benefited from offshore development across multiple businesses: The smart choice, or how to select the right offshore development partner Warning signs, or how to minimize chances of making the wrong choice Collaboration, or how to establish the most effective work processes Budget control, or how to maximize project result...
    In his keynote at 19th Cloud Expo, Sheng Liang, co-founder and CEO of Rancher Labs, discussed the technological advances and new business opportunities created by the rapid adoption of containers. With the success of Amazon Web Services (AWS) and various open source technologies used to build private clouds, cloud computing has become an essential component of IT strategy. However, users continue to face challenges in implementing clouds, as older technologies evolve and newer ones like Docker c...
    For organizations that have amassed large sums of software complexity, taking a microservices approach is the first step toward DevOps and continuous improvement / development. Integrating system-level analysis with microservices makes it easier to change and add functionality to applications at any time without the increase of risk. Before you start big transformation projects or a cloud migration, make sure these changes won’t take down your entire organization.
    Without a clear strategy for cost control and an architecture designed with cloud services in mind, costs and operational performance can quickly get out of control. To avoid multiple architectural redesigns requires extensive thought and planning. Boundary (now part of BMC) launched a new public-facing multi-tenant high resolution monitoring service on Amazon AWS two years ago, facing challenges and learning best practices in the early days of the new service.
    You often hear the two titles of "DevOps" and "Immutable Infrastructure" used independently. In his session at DevOps Summit, John Willis, Technical Evangelist for Docker, covered the union between the two topics and why this is important. He provided an overview of Immutable Infrastructure then showed how an Immutable Continuous Delivery pipeline can be applied as a best practice for "DevOps." He ended the session with some interesting case study examples.
    Both SaaS vendors and SaaS buyers are going “all-in” to hyperscale IaaS platforms such as AWS, which is disrupting the SaaS value proposition. Why should the enterprise SaaS consumer pay for the SaaS service if their data is resident in adjacent AWS S3 buckets? If both SaaS sellers and buyers are using the same cloud tools, automation and pay-per-transaction model offered by IaaS platforms, then why not host the “shrink-wrapped” software in the customers’ cloud? Further, serverless computing, cl...
    "We view the cloud not as a specific technology but as a way of doing business and that way of doing business is transforming the way software, infrastructure and services are being delivered to business," explained Matthew Rosen, CEO and Director at Fusion, in this SYS-CON.tv interview at 18th Cloud Expo (http://www.CloudComputingExpo.com), held June 7-9 at the Javits Center in New York City, NY.
    Without lifecycle traceability and visibility across the tool chain, stakeholders from Planning-to-Ops have limited insight and answers to who, what, when, why and how across the DevOps lifecycle. This impacts the ability to deliver high quality software at the needed velocity to drive positive business outcomes. In his general session at @DevOpsSummit at 19th Cloud Expo, Eric Robertson, General Manager at CollabNet, will discuss how customers are able to achieve a level of transparency that e...
    We all know that end users experience the internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices - not doing so will be a path to eventual ...
    "DivvyCloud as a company set out to help customers automate solutions to the most common cloud problems," noted Jeremy Snyder, VP of Business Development at DivvyCloud, in this SYS-CON.tv interview at 20th Cloud Expo, held June 6-8, 2017, at the Javits Center in New York City, NY.
    We all know that end users experience the Internet primarily with mobile devices. From an app development perspective, we know that successfully responding to the needs of mobile customers depends on rapid DevOps – failing fast, in short, until the right solution evolves in your customers' relationship to your business. Whether you’re decomposing an SOA monolith, or developing a new application cloud natively, it’s not a question of using microservices – not doing so will be a path to eventual b...
    "This all sounds great. But it's just not realistic." This is what a group of five senior IT executives told me during a workshop I held not long ago. We were working through an exercise on the organizational characteristics necessary to successfully execute a digital transformation, and the group was doing their ‘readout.' The executives loved everything we discussed and agreed that if such an environment existed, it would make transformation much easier. They just didn't believe it was reali...
    "Opsani helps the enterprise adopt containers, help them move their infrastructure into this modern world of DevOps, accelerate the delivery of new features into production, and really get them going on the container path," explained Ross Schibler, CEO of Opsani, and Peter Nickolov, CTO of Opsani, in this SYS-CON.tv interview at DevOps Summit at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    Most companies are adopting or evaluating container technology - Docker in particular - to speed up application deployment, drive down cost, ease management and make application delivery more flexible overall. As with most new architectures, this dream takes a lot of work to become a reality. Even when you do get your application componentized enough and packaged properly, there are still challenges for DevOps teams to making the shift to continuous delivery and achieving that reduction in cost ...
    Your homes and cars can be automated and self-serviced. Why can't your storage? From simply asking questions to analyze and troubleshoot your infrastructure, to provisioning storage with snapshots, recovery and replication, your wildest sci-fi dream has come true. In his session at @DevOpsSummit at 20th Cloud Expo, Dan Florea, Director of Product Management at Tintri, provided a ChatOps demo where you can talk to your storage and manage it from anywhere, through Slack and similar services with...
    "I focus on what we are calling CAST Highlight, which is our SaaS application portfolio analysis tool. It is an extremely lightweight tool that can integrate with pretty much any build process right now," explained Andrew Siegmund, Application Migration Specialist for CAST, in this SYS-CON.tv interview at 21st Cloud Expo, held Oct 31 – Nov 2, 2017, at the Santa Clara Convention Center in Santa Clara, CA.
    Explosive growth in connected devices. Enormous amounts of data for collection and analysis. Critical use of data for split-second decision making and actionable information. All three are factors in making the Internet of Things a reality. Yet, any one factor would have an IT organization pondering its infrastructure strategy. How should your organization enhance its IT framework to enable an Internet of Things implementation? In his session at @ThingsExpo, James Kirkland, Red Hat's Chief Archi...