서비의 다락방

Java API for XML Web Services (JAX-WS) 2.0, JSR 224, is an important part of the Java EE 5 platform. A follow-on release of Java API for XML-based RPC 1.1(JAX-RPC), JAX-WS simplifies the task of developing web services using Java technology. It addresses some of the issues in JAX-RPC 1.1 by providing support for multiple protocols such as SOAP 1.1, SOAP 1.2, XML, and by providing a facility for supporting additional protocols along with HTTP. JAX-WS uses JAXB 2.0 for data binding and supports customizations to control generated service endpoint interfaces. With its support for annotations, JAX-WS simplifies web service development and reduces the size of runtime JAR files.

This document takes you through the basics of using the IDE to develop a JAX-WS web service and to consume it in three different clients—either a Java class in a Java SE application, or a servlet or JSP page in a web application. The three clients that you create in this document are separate applications, all consuming the same web service.

Expected duration: 25 minutes

Installing and Configuring the Tutorial Environment

If you have not registered an instance of the Sun Java System Application Server 9.0, you must do so before you can begin developing Java EE 5 applications:

1. Choose Tools > Server Manager from the main window.
2. Click Add Server. Select Sun Java System Application Server and give a name to the instance. Then click Next.
3. Specify the server information, the location of the local instance of the application server, and the domain to which you want to deploy.
4. Click Finish.

Note: If you want to deploy to the Tomcat Web Server, you can do so, except that, since it only has a web container, you should create a web application, not an EJB module, in the next section. JAX-WS web services, unlike JSR-109 web services, can deploy successfully to the Tomcat web container.

Creating a Web Service

The goal of this exercise is to create a project appropriate to the deployment container that you decide to use. Once you have a project, you will create a web service in it.

Coding the Web Service

The goal of this exercise is to do something meaningful with the files and code that the IDE has generated for you. You will add an operation that will add two numbers received from a client.

Deploying and Testing the Web Service

When you deploy a web service to a web container, the IDE lets you test the web service to see if it functions as you expect. The Tester application, provided by the Sun Java System Application Server, is integrated into the IDE for this purpose. For the Tomcat Web Server, there is a similar tool. However, while the Sun Java System Application Server's Tester page lets you enter values and test them, the Tomcat Web Server does not. In the latter case, you can only see that the web service is deployed, you cannot test the values. No facility for testing whether an EJB module is deployed successfully is currently available.

To test successful deployment to a web container:

1. Right-click the project node, choose Properties, and click Run. Depending on the deployment server that you want to use, do the following:
   • For the Sun Java System Application Server, type /CalculatorWSService?Tester in the Relative URL field.
   • For the Tomcat Web Server, type /CalculatorWS?Tester in the Relative URL field.

   Note: Since the result of a deployed EJB module is not displayed in a browser, you cannot take the step above if you are working with an EJB module.

2. Right-click the project node and choose Run Project.

   The IDE starts the application server, builds the application, and opens the tester page in your browser, if you deployed a web application to the Sun Java System Application Server. For the Tomcat Web Server and deployment of EJB modules, the situation is different:

   • If you deployed to the Tomcat Web Server, you will see the following instead, which indicates that you have successfully deployed your web service:

     

   • If you deployed an EJB module, successful deployment is indicated by the following messages in the Output window:

         Deployment of application CalculatorWSApplication  completed successfully
         Enable of CalculatorWSApplication in target server   completed successfully
         Enable of application in all targets  completed successfully
         All operations completed successfully
         run-deploy:
         run:
         BUILD SUCCESSFUL

   • If you deployed to the Sun Java System Application Server, type two numbers in the tester page, as shown below:

     

     The sum of the two numbers is displayed:

     

Summary

In this exercise, you deployed a web service and tested it.

Consuming the Web Service

Now that we have deployed our web service, we need to create a client to make use of the web service's add method. Here, we create three clients— a Java class in a Java SE application, a servlet, and a JSP page in a web application.

Contents

• Overview
• Software Needed for this Tutorial
• Configuring the Tutorial Environment
• Creating the Project
• Creating the WSDL Document
• Creating the BPEL Process
• Creating the Composite Application
• Using the CASA Editor
• Deploying and Testing the Composite Application

Overview

You will be creating a simple SOA project. You will add a WSDL file to your BPEL Module project. You use the Partner view to add the messages, partner link type, port type, and operation. Then you will create a composite application project and use the CASA editor to modify the project configuration. This tutorial also illustrates a basic scenario of how a File Binding Component can be used in a composite application.

Software Needed for this Tutorial

Before you begin, you must install the following software on your computer:

• NetBeans IDE 5.5.1 Beta with NetBeans Enterprise Pack 5.5.1 Beta

Configuring the Tutorial Environment

Before you can deploy your application, the Sun Java System Application Server and JBI runtime must be configured correctly and running.

To configure the tutorial environment:

1. Click the Runtime tab to open the Runtime window.
2. In the Runtime window, expand the Servers node.
3. If the Servers node already contains a Sun Java System Application Server 9 node, then go to step 5.
4. If the Servers node does not contain a Sun Java System Application Server 9 node, then do the following to add an application server:
   
   1. Right-click the Servers node and choose Add Server from the pop-up menu.
      The Add Server Instance dialog box opens.
   2. In the Choose Server page, from the Server drop-down list, select Sun Java System Application Server.
   3. (Optional) In the Name field, accept the default value or type the name you want to use to identify the server in the IDE.
   4. Click Next.
      The Platform Location Folder page opens.
   5. In the Platform Location field, use the Browse button to navigate to and select the Application Server installation location.
      If you accepted the default values during the installation, the location is C:\Sun\Appserver .
   6. Select the Register Local Default Domain radio button.
   7. Click Next.
   8. Supply the user name and password for the domain's administrator.
      If you accepted the default values during the installation, the user name is admin and the password is adminadmin .
   9. Click Finish.
5. In the Runtime window, right-click the Sun Java System Application Server 9 node and choose Start.
   If the Start option is not available, the server is already running and you can skip the next step.
6. Wait until the following message appears in the Output window:
   Application server startup complete.
   When the server is running, the IDE displays a green arrow badge on the Sun Java System Application Server 9 node.

Creating the Project

In this section, you create a BPEL Module project called HelloSample .

To create the HelloSample project:

1. From the IDE's main menu, choose File > New Project.
   The New Project wizard opens.
2. In the Categories list, select the Service Oriented Architecture node.
3. In the Projects list, select the BPEL Module node.
4. Click Next.
5. In the Project Name field, type HelloSample .
6. (Optional) In the Project Location field, use the Browse button to navigate to and select a different folder where the IDE will store the project files.
7. Click Finish.
   The Projects window now contains a project node for a BPEL Module project called HelloSample .

Creating the WSDL Document

In this section, you add a WSDL file to your BPEL Module project and then use Partner view to configure the components of the WSDL Document.

To create HelloSample.wsdl :

1. In the Projects window, expand the HelloSample project node, then right-click the Process Files node and choose New > WSDL Document.
   The New WSDL Document wizard opens.
2. In the File Name field, type HelloSample .
3. Click Finish.
4. The IDE does the following:
   
   • Creates HelloSample.wsdl node under the Process Files.
   • Opens the HelloSample.wsdl in the source editor.
     The Source Editor contains 3 tabs for the WSDL file, Source, WSDL, and Partner, with the WSDL view opened.
   • Opens the Properties window. If the Properties window is not visible, choose Window > Properties.
5. In the WSDL view, click the Partner button to open the Partner view of the WSDL editor.
   The IDE opens the WSDL Palette. If the Palette window is not visible, choose Window > Palette from the main menu.
   You can create the SequenceDiagram in this view.

To add Messages :

1. In the Palette of the Partner view select the Message icon.
   
2. Drag your selection to the WSDL Partner View design area, below the Messages.
   The IDE adds a Message and the name of the new Message is ( Messages1 ).
3. Click the down arrow to expand the new message. If the arrow is up, the message is already expanded.
   The design area now shows Part Name and Part element or Type columns.
4. In the Message Part Name column, double-click the default value (part1) to make the field editable.
5. Type inputType and press Enter. If the Message1 is collapsed, click the down arrow to expand the new message
6. In the Part Element Or Type column, make sure the default type is xsd:string
   If the type is not string then click the ellipsis button and select BuiltIn Schema Types > Built-in Types > String
7. Repeat step 1-6 and for the Message Part Name, enter resultType.

To add PartnerLinkType :

1. In the Palette of the Partner view select the PartnerLinkType icon.
2. Drag your selection to the WSDL Partner View design area, below the PartnerLinkTypes(0).
   The IDE adds a PartnerLink and is ready to create new Roles and Port Types. Roles and PortTypes are drawn as dotted vertical lines( Lifeline) with the External names showing at the top.
3. For Port Types double click the green rectangle under the role1 node.
4. Click Enter. The new portType1 is assigned.
5. In the Palette of the Partner view select the Request-Response icon.
6. Drag your selection to the WSDL Partner View design area, below the portType1.
   The new Operation, operation1 is added.
7. Under operation1, double click the upper message arrow where it says <No Message Selected> and select tns:message1.
8. Repeat step 7and 8 for the lower message arrow and select tns:message2.

Creating the BPEL Process

To create HelloSample.bpel :

1. In the Projects window, expand the HelloSample project node, then right-click the Process Files node and choose New > BPEL Process.
   The New BPEL Process wizard opens.
2. In the File Name field, type HelloSample.
3. Click Finish.
   The Sample.bpel is created

To add a partner link:

1. In the Web Service section of the Palette, select the Partner Link icon and drag your selection to the design area.
   The Create New Partnerlink1Property Editor opens.
2. Accept the defaults and click OK.

To add a Receive activity:

1. In the Web Service section of the Palette, select the Receive icon and drag your selection to the design area between the Process Start activity and the Process End activity.
   The IDE provides you with visual clues to show you where you can drop the selection.
   This action places a Receive activity called Receive1 in the Design view.
2. Double-click the Receive1 activity.
   The Receive1 [Receive] - Property Editor opens.
3. From the Partner Link drop-down list, select PartnerLink1.
   The IDE fills in the Operation field.
4. Create a new input variable by doing the following:
   1. Click the Create button next to the Input Variable field.
      The New Input Variable dialog box opens.
   2. Change the value in the Name field to inputVar .
   3. Click OK.
5. Click OK to close the Receive1 [Receive] - Property Editor.
   The Receive activity is now labeled start in the Design view.

To add a Reply activity:

1. In the Web Service section of the Palette, select the Reply icon and drag your selection to the design area between the Receive1 activity and the Process End activity.
   The IDE provides you with visual clues to show you where you can drop the selection.
   This action places a Reply activity called Reply1 in the Design view.
2. Double-click the Reply1 activity.
   The Reply1 [Reply] - Property Editor opens.
3. From the Partner Link drop-down list, select PartnerLink1.
   The IDE fills in the Operation field.
4. Create a new output variable by doing the following:
   1. Make sure the Normal Response radio button is selected.
   2. Click the Create button next to the Output Variable field.
      The New Output Variable dialog box opens.
   3. Change the value in the Name field to outputVar .
   4. Click OK.
5. Click OK to close the Reply1 [Reply] - Property Editor.
   The Reply activity is now labeled end in the Design view.

To add an Assign activity:

1. In the Basic Activities section of the Palette, select the Assign icon and drag your selection to the design area between the Receive1 activity and the Reply1 activity.
   This action places an Assign activity called Assign1 in the Design view.
2. Select the Assign1 activity.
3. If the BPEL Mapper window is not visible, choose Window > BPEL Mapper from the main menu.
4. In the left pane of the BPEL Mapper, under Variables, expand the inputVar node.
   inputType appears under inputVar .
5. In the right pane of the BPEL Mapper, under Variables, expand the outputVar node.
   resultType appears under outputVar .
6. Drag inputType from the left pane of the BPEL Mapper to the resultType node in the right pane of the BPEL Mapper.
   This assignment copies the input statement into the output.
7. To save your changes, in the Projects window, select the SynchronousSample project node, and from the IDE's main menu, choose File > Save All.

Creating the Composite Application

Before you deploy the BPEL Module project, you must add the JBI module to the deployment project. Deploying the project makes the service assembly available to the application server, thus allowing its service units to be run.

To create the Composite Application project:

1. From the IDE's main menu, choose File > New Project.
   The New Project wizard opens.
2. In the Categories list, select the Service Oriented Architecture node.
3. In the Projects list, select the Composite Application node.
4. Click Next.
5. In the Project Name field, type SampleCompositeApp .
6. Click Finish.
   The Projects window now contains a project node for a Composite Application project called SampleCompositeApp .

Using the CASA Editor

To use the CASA editor to modify the project configuration:

1. Right click on the SampleCompositeApp project and select Edit Project.
2. Click on the HelloSample node and drag-n-drop it onto the JBI module area.
   
   
   
   
3. Click the build button on CASA toolbar to build the bpel project.

To create the WSDL endpoint:

1. Click on the "file" palette item on the WSDL Bindings category in the Palette panel.
2. Drag-n-drop it to the WSDL Ports area in the CASA editor.
3. A new "casasport1" WSDL endpoint is added.
   
   

To createa new connection:

1. Click on the consume endpoint of the new port.
2. Drag it to the erole1_myRole to create a new connection.
   
   

To Check auto-generated WSDL endpoint properties

1. In the Navigator panel, expand the WSDL Ports node.
2. Expand casaPort1 > casaBinding1 > operation1 > input1.
3. Select file:message.
4. In the Properties window, assign use='literal" , pollingIntervl=5000 and fileName=input.txt.
5. Click on WSDL Ports area in the CASA editor to open the Navigator panel again.
6. In the Navigator panel, expand WSDL Ports > casaPort1 > casaBinding1 > operation1 > output1.
7. Select file:message.
8. In the Properties window, assign fileName=output.txt.
9. Click on WSDL Ports area in the CASA editor to open the Navigator panel.
10. In the Navigator panel, expand the WSDL Ports node.
11. Expand casaPort1 ->casaPort1 to select the file:address node.
12. In the Properties window, in the fileDirectory, replace C:/Temp with the string c:/temp.
13. Click Ok.

Deploying and Testing the SampleCompositeApp

To deploy the Composite Application:

1. Right-click the SampleCompositeApp project node and choose Deploy Project.
   If a message similar to the following message appears in the Output window, then the deployment has succeeded:
   BUILD SUCCESSFUL (total time: 11 seconds)

To test the SampleCompositeApp:

1. Create the input.txt file in c:/temp folder and edit the file to content 'Hello World!!'.
2. input.txt will be renamed to input.txt_processed.
3. output.txt will be created in the same folder with the same content 'Hello World!!'.

@http://blogs.sun.com/barkodar/resource/HelloSample.html