2002/ws/desc/wsdl20 wsdl20-primer.html,1.130,1.131 wsdl20-primer.xml,1.144,1.145

Update of /sources/public/2002/ws/desc/wsdl20
In directory hutz:/tmp/cvs-serv4592/ws/desc/wsdl20

Modified Files:
	wsdl20-primer.html wsdl20-primer.xml 
Log Message:
fixed typo in section 2.1.1

Index: wsdl20-primer.xml
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.xml,v
retrieving revision 1.144
retrieving revision 1.145
diff -C2 -d -r1.144 -r1.145
*** wsdl20-primer.xml	13 Feb 2006 22:34:44 -0000	1.144
--- wsdl20-primer.xml	13 Feb 2006 22:55:46 -0000	1.145
***************
*** 146,150 ****
  			<p>This section introduces the basic concepts used in WSDL 2.0 through the description of a hypothetical hotel reservation service. We start with a simple scenario, and later add more requirements to illustrate how more advanced WSDL 2.0 features may be used. </p>
  
! 			<!-- ************************ GreatH *************************** --><div3 id="basics-greath-scenario"><head>Example Scenario: The GreatH Hotel Reservation Service</head><p>Hotel GreatH (a fictional hotel)) is located in a remote island. It has been relying on fax and phone to provide room reservations. Even though the facilities and prices at GreatH are better than what its competitor offers, GreatH notices that its competitor is getting more customers than GreatH.   After research, GreatH realizes that this is because the  competitor offers a Web service that permits travel agent reservation systems to reserve rooms directly over the Internet.  GreatH then hires us to build a reservation Web service with the following functionality:  <ulist><item><p><emph>CheckAvailability</emph>. To check availability, the client must specify a check-in date, a check-out date, and room type.  The Web service will return a room rate (a floating point number in USD$) if such a room is available, or a zero room rate if ot. If any input data is invalid, the service should return an error.  Thus, the service will accept a <code>checkAvailability</code> message and return a <code>checkAvailabilityResponse</code> or <code>invalidDataFault</code> message.</p>  </item><item><p><emph>MakeReservation</emph>.  To make a reservation, a client must provide a name, address, and credit card information, and the service will return a confirmation number if the reservation is successful.  The service will return an error message if the credit card number or any other data field is invalid.  Thus, the service will accept a <code>makeReservation</code> message and return a <code>makeReservationResponse</code> or <code>invalidCreditCardFault</code> message.</p></item></ulist> We know that we will later need to build a complete system that supports transactions and secured transmission, but initially we will implement only minimal functionality.  In fact, to simplify our first example, we will implement only the <emph>CheckAvailability</emp> operation.  </p><p>The next several sections proceed step-by-step through the process of developing a WSDL 2.0 document that describes the desired Web service.  However, for those who can't wait to see a complete example, here is the WSDL 2.0 document that we'll be creating.</p><example id="example-initial">
  					<head>WSDL 2.0 Document for the GreatH Web Service (Initial Example)</head>
  					<eg><![CDATA[
--- 146,150 ----
  			<p>This section introduces the basic concepts used in WSDL 2.0 through the description of a hypothetical hotel reservation service. We start with a simple scenario, and later add more requirements to illustrate how more advanced WSDL 2.0 features may be used. </p>
  
! 			<!-- ************************ GreatH *************************** --><div3 id="basics-greath-scenario"><head>Example Scenario: The GreatH Hotel Reservation Service</head><p>Hotel GreatH (a fictional hotel) is located in a remote island. It has been relying on fax and phone to provide room reservations. Even though the facilities and prices at GreatH are better than what its competitor offers, GreatH notices that its competitor is getting more customers than GreatH.   After research, GreatH realizes that this is because the  competitor offers a Web service that permits travel agent reservation systems to reserve rooms directly over the Internet.  GreatH then hires us to build a reservation Web service with the following functionality:  <ulist><item><p><emph>CheckAvailability</emph>. To check availability, the client must specify a check-in date, a check-out date, and room type.  The Web service will return a room rate (a floating point number in USD$) if such a room is available, or a zero room rate if nt. If any input data is invalid, the service should return an error.  Thus, the service will accept a <code>checkAvailability</code> message and return a <code>checkAvailabilityResponse</code> or <code>invalidDataFault</code> message.</p>  </item><item><p><emph>MakeReservation</emph>.  To make a reservation, a client must provide a name, address, and credit card information, and the service will return a confirmation number if the reservation is successful.  The service will return an error message if the credit card number or any other data field is invalid.  Thus, the service will accept a <code>makeReservation</code> message and return a <code>makeReservationResponse</code> or <code>invalidCreditCardFault</code> message.</p></item></ulist> We know that we will later need to build a complete system that supports transactions and secured transmission, but initially we will implement only minimal functionality.  In fact, to simplify our first example, we will implement only the <emph>CheckAvailability</emph operation.  </p><p>The next several sections proceed step-by-step through the process of developing a WSDL 2.0 document that describes the desired Web service.  However, for those who can't wait to see a complete example, here is the WSDL 2.0 document that we'll be creating.</p><example id="example-initial">
  					<head>WSDL 2.0 Document for the GreatH Web Service (Initial Example)</head>
  					<eg><![CDATA[

Index: wsdl20-primer.html
===================================================================
RCS file: /sources/public/2002/ws/desc/wsdl20/wsdl20-primer.html,v
retrieving revision 1.130
retrieving revision 1.131
diff -C2 -d -r1.130 -r1.131
*** wsdl20-primer.html	13 Feb 2006 22:34:44 -0000	1.130
--- wsdl20-primer.html	13 Feb 2006 22:55:46 -0000	1.131
***************
*** 176,180 ****
  
  			<div class="div3">
! <h4><a name="basics-greath-scenario"></a>2.1.1 Example Scenario: The GreatH Hotel Reservation Service</h4><p>Hotel GreatH (a fictional hotel)) is located in a remote island. It has been relying on fax and phone to provide room reservations. Even though the facilities and prices at GreatH are better than what its competitor offers, GreatH notices that its competitor is getting more customers than GreatH.   After research, GreatH realizes that this is because the  competitor offers a Web service that permits travel agent reservation systems to reserve rooms directly over the Internet.  GreatH then hires us to build a reservation Web service with the following functionality:  <ul><li><p><em>CheckAvailability</em>. To check availability, the client must specify a check-in date, a check-out date, and room type.  The Web service will return a room rate (a floating point number in USD$) if such a room is available, or a zero room rate if not. If any input data is invalid, the service should return an error.  Thu, the service will accept a <code>checkAvailability</code> message and return a <code>checkAvailabilityResponse</code> or <code>invalidDataFault</code> message.</p>  </li><li><p><em>MakeReservation</em>.  To make a reservation, a client must provide a name, address, and credit card information, and the service will return a confirmation number if the reservation is successful.  The service will return an error message if the credit card number or any other data field is invalid.  Thus, the service will accept a <code>makeReservation</code> message and return a <code>makeReservationResponse</code> or <code>invalidCreditCardFault</code> message.</p></li></ul> We know that we will later need to build a complete system that supports transactions and secured transmission, but initially we will implement only minimal functionality.  In fact, to simplify our first example, we will implement only the <em>CheckAvailability</em> operation.  </p><p>The next several sections proceed step-by-step through the process of eveloping a WSDL 2.0 document that describes the desired Web service.  However, for those who can't wait to see a complete example, here is the WSDL 2.0 document that we'll be creating.</p><div class="exampleOuter">
  					<p style="text-align: left" class="exampleHead"><a name="example-initial"></a><i><span>Example 2-1. </span>WSDL 2.0 Document for the GreatH Web Service (Initial Example)</i></p>
  					<div class="exampleInner"><pre>
--- 176,180 ----
  
  			<div class="div3">
! <h4><a name="basics-greath-scenario"></a>2.1.1 Example Scenario: The GreatH Hotel Reservation Service</h4><p>Hotel GreatH (a fictional hotel) is located in a remote island. It has been relying on fax and phone to provide room reservations. Even though the facilities and prices at GreatH are better than what its competitor offers, GreatH notices that its competitor is getting more customers than GreatH.   After research, GreatH realizes that this is because the  competitor offers a Web service that permits travel agent reservation systems to reserve rooms directly over the Internet.  GreatH then hires us to build a reservation Web service with the following functionality:  <ul><li><p><em>CheckAvailability</em>. To check availability, the client must specify a check-in date, a check-out date, and room type.  The Web service will return a room rate (a floating point number in USD$) if such a room is available, or a zero room rate if not. If any input data is invalid, the service should return an error.  Thus the service will accept a <code>checkAvailability</code> message and return a <code>checkAvailabilityResponse</code> or <code>invalidDataFault</code> message.</p>  </li><li><p><em>MakeReservation</em>.  To make a reservation, a client must provide a name, address, and credit card information, and the service will return a confirmation number if the reservation is successful.  The service will return an error message if the credit card number or any other data field is invalid.  Thus, the service will accept a <code>makeReservation</code> message and return a <code>makeReservationResponse</code> or <code>invalidCreditCardFault</code> message.</p></li></ul> We know that we will later need to build a complete system that supports transactions and secured transmission, but initially we will implement only minimal functionality.  In fact, to simplify our first example, we will implement only the <em>CheckAvailability</em> operation.  </p><p>The next several sections proceed step-by-step through the process of dveloping a WSDL 2.0 document that describes the desired Web service.  However, for those who can't wait to see a complete example, here is the WSDL 2.0 document that we'll be creating.</p><div class="exampleOuter">
  					<p style="text-align: left" class="exampleHead"><a name="example-initial"></a><i><span>Example 2-1. </span>WSDL 2.0 Document for the GreatH Web Service (Initial Example)</i></p>
  					<div class="exampleInner"><pre>

Received on Monday, 13 February 2006 22:55:59 UTC