Getting Started with WebSphere Application Server

More documents

Recommendations

Info

130 Getting Started with WebSphere Application Server Community Edition portName = "HelloBillPort", endpointInterface = "com.ibm.wasce.samples.HelloPeople", targetNamespace = "http://samples.wasce.ibm.com") public class HelloBill implements HelloPeople { public String sayHello(String targetName) { return "Hello " + targetName; } } Listing 7.2 – SEI’s implementation: HelloBill.java The @WebService annotation properties serviceName, portName, and targetNamespace shown in the above listing are sample values. It is fine to provide the @WebService annotation only with values for the endpointInterface property and use defaults for the rest. 7.2.4 Deploying the Web Service in Community Edition To publish a Web Service in Community Edition, you need to add some information under the and elements in the Web project’s WEB- INF/web.xml file. However, this does not mean that the service class must be a Servlet, which must extend the HttpServlet. The Web service is never a real servlet; the deployer of Community Edition can distinguish whether or not it is a Web service implementation class. Listing 7.3 provides an example of the contents of web.xml. Hello com.ibm.wasce.samples.HelloBill Hello /Hello Listing 7.3 - The web.xml file The element defines how to invoke the Web service from a browser and also the path to retrieve its WSDL file. After deploying the Web project to Community Edition, launch a browser and go to the following URL: http://localhost:8080/HelloServiceProject/Hello You should see a message from the Axis2 engine as shown in Figure 7.2 below.
Chapter 7 – Web services 131 Figure 7.2 – Message from the Axis2 engine And you can get the WSDL file generated by Geronimo from the following location: http://localhost:8080/HelloServiceProject/Hello?wsdl 7.3 Consuming a Web Service deployed in Community Edition To test and invoke (consume) a Web service from a client, follow these steps: 1. Review the WSDL from a browser, and use jaxws-tools to generate stub classes. 2. Import stubs into your client application. 3. Construct a Service object through the stubs, and get the target port object from the service; then, invoke the methods on the port object. This section will show you how to create a POJO client and a Web-based client for a Web service. You only need the WSDL file of the Web service deployed for creating the client. 7.3.1 Creating necessary stubs to consume the Web Service You need to create a Service Endpoint Interface based on the WSDL document by using the JAX-WS tool wsimport. The syntax to use this tool is: wsimport [options] Common options of wsimport are shown in Table 7.1:
Page 3 and 4:
G E T T I N G S T A R T E D W I T H
Page 5 and 6:
Notices This information was develo
Page 7 and 8:
Trademarks IBM, the IBM logo, and i
Page 9 and 10:
3.8 Exercises .....................
Page 11 and 12:
9.3.2 Changing port numbers .......
Page 13 and 14:
13 Preface Keeping your skills curr
Page 15:
The DB2 on Campus book series 15
Page 18 and 19:
18 Getting Started with WebSphere A
Page 21 and 22:
1 Chapter 1 - Introduction to WebSp
Page 23 and 24:
Introduction to WebSphere Applicati
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 47 and 48:
3 Chapter 3 - Development with Comm
Page 49 and 50:
Chapter 3 - Development with Commun
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
4 Chapter 4 - Working with database
Page 67 and 68:
Chapter 4 - Working with databases
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80: Chapter 4 - Working with databases
Page 89 and 90: 5 Chapter 5 - Enterprise Java Beans
Page 91 and 92: 1. Define local and remote interfac
Page 93 and 94: Chapter 5 - Enterprise Java Beans 9
Page 97 and 98: Note: Chapter 5 - Enterprise Java B
Page 109 and 110: 6 Chapter 6 - Messaging Messaging i
Page 111 and 112: Chapter 6 - Messaging 111 3. Messag
Page 113 and 114: Chapter 6 - Messaging 113 2. Get JM
Page 115 and 116: Chapter 6 - Messaging 115 Figure 6.
Page 117 and 118: Chapter 6 - Messaging 117 Figure 6.
Page 119 and 120: Chapter 6 - Messaging 119 For examp
Page 121 and 122: textMessage.getText()); } catch (JM
Page 123 and 124: Chapter 6 - Messaging 123 3. Copy t
Page 125: Chapter 6 - Messaging 125 D. Messag
Page 128 and 129: 128 Getting Started with WebSphere
Page 161: PART III - ADMINISTERING COMMUNITY
Page 181 and 182:
10 Chapter 10 - Tuning a Community
Page 183 and 184:
Chapter 10 - Tuning a Community Edi
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
10.4.2 Operating system tuning Chap
Page 193:
Page 196 and 197:
196 Getting Started with WebSphere
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 211 and 212:
A Appendix A - Solutions to review
Page 213 and 214:
Appendix A - Solutions to review qu
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
B Appendix B - Up and running with
Page 221 and 222:
Appendix B - Up and running with DB
Page 223 and 224:
4. The following is performed by de
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235:
C Appendix C - Using the sample cod
Page 238 and 239:
Page 240:
show all

Getting Started with WebSphere Application Server

Create successful ePaper yourself

Delete template?

Save as template?