# Summary: Web Service Tutorial

This topic lists ideas this tutorial introduced, along with links to topics for more information. You may also find it useful to look at the following:

- For an overview of WebLogic Workshop, see Building Web Services with WebLogic Workshop.
- For a links to information on tasks you can accomplish in WebLogic Workshop, see the How Do I? topics.
- For a list of the samples provided, see Samples.

## Concepts and Tasks Introduced in This Tutorial

- You interact with web service source files through a WebLogic Workshop project. You use projects to group files associated with a web service or related web services.

  For more information about projects, see Applications and Projects.

- As you develop web services, you test and debug code on a running instance of WebLogic Server.
- You design a web service as you might make a drawing of it and its relationships with clients and other resources. WebLogic Workshop provides a Design View you can use to generate code to start with as you create your design.
- The source file for a web service is a JWS file, which is automatically recognized as a web service when deployed with WebLogic Server.
- You expose the functionality of a web service by creating methods within a JWS file. You can add the method in Design View, setting properties to specify its characteristics, including powerful server features.
- To test a service, you use the Test View, a dynamically generated HTML page through which you can invoke service methods with specific parameter values.
- You can use asynchronous communications to handle latency issues inherent on the Internet, and sometimes with web services in general. Through asynchrony, you avoid situations in which client software is blocked from proceeding until it receives the results of its requests.

  For an introduction to asynchrony and the WebLogic Workshop tools that support it, see Designing Asynchronous Interfaces.

- Callbacks provide a useful way to return results to clients where asynchronous communication is needed. Callbacks require an agreement that the client will implement a means to handle the callback a service makes.
  For more details, see Using Callbacks to Notify Clients of Events.
- You can use conversations to maintain consistent state even between disparate asynchronous exchanges. Conversations make it possible to correlate these exchanges with the original request and the client that made it.

  For more information, see Designing Conversational Web Services and Getting Started: Using Asynchrony to Enable Long-Running Operations.

- When you need to handle or control the specific shape of XML messages your service exchanges with other components, you can use Workshop's extensive XML tools such as XQuery and XMLBeans.
  For more on Workshop's XML tools, see Getting Started with XMLBeans and Transforming XML Messages with XQuery Maps.
- By supporting polling, your web service can offer an alternative to clients that aren't capable of receiving callbacks. With polling, a client can periodically ask your web service if the response to its request is ready yet.

  For information about polling, see Using Polling as an Alternative to Callbacks.

- You can make your web service secure with WS-Security or more traditional transport security.

  For more detail, see Web Service Security and Transport Security.