10.15. Testing Web Services Deployment
It's taken us a while to get here, but now that we have the core infrastructure in place to deploy a Web Service, let's test our deployment. Here are the steps to build and deploy the application:
You should see the following output in the JBoss console:
... 23:08:11,921 INFO [WSDLFilePublisher] WSDL published to: file:/C:/jboss- 4.0.2/server/default/data/wsdl/jaw.ear/ejb.jar/InventoryService.wsdl 23:08:12,182 INFO [AxisService] WSDD published to: C:\jboss- 4.0.2\server\default\data\wsdl\jaw.ear\ejb.jar\Inventory.wsdd 23:08:12,632 INFO [AxisService] Web Service deployed: http://localhost:8080/jbossatwork-ws/InventoryService ...
Now point your browser to http://localhost:8080/ws4ee to see the JBossWS page as shown in Figure 10-2.
Figure 10-2. JBossWS page
Clicking on the "View the list of deployed Web services" link takes you to the JBoss Deployed Web Services Page, as depicted in Figure 10-3.
Figure 10-3. JBoss Deployed Web Services page
At this point, you'll see our Web Service (findAvailableCars) listed under jaw.ear/ejb.jar#Inventory. Click on the wsdl link, and you'll see the WSDL for our Web Service.
Now that we've successfully deployed our Web Service and viewed the WSDL, keep JBoss running. We now move on to develop an external client that calls the findAvailableCars Web Service.