You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by to...@apache.org on 2004/12/31 02:35:07 UTC

cvs commit: ws-axis/site/src/documentation/content/xdocs/docs CachingEarlDraft2.xml

toshi       2004/12/30 17:35:07

  Modified:    site/src/documentation/content/xdocs/docs
                        CachingEarlDraft2.xml
  Log:
  Removed the name - 'nagoya'.
  
  Revision  Changes    Path
  1.2       +1 -1      ws-axis/site/src/documentation/content/xdocs/docs/CachingEarlDraft2.xml
  
  Index: CachingEarlDraft2.xml
  ===================================================================
  RCS file: /home/cvs/ws-axis/site/src/documentation/content/xdocs/docs/CachingEarlDraft2.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- CachingEarlDraft2.xml	16 Oct 2003 18:48:11 -0000	1.1
  +++ CachingEarlDraft2.xml	31 Dec 2004 01:35:07 -0000	1.2
  @@ -281,7 +281,7 @@
   <H1 id="section6">6. Appendix: Sample Application</H1>
   <DIV>
     This sample application uses the WeatherForecastService to enable a cacheable scenario. When
  -an end-user sets a location (like as Tokyo, Osaka, or Nagoya) and invokes the service, the
  +an end-user sets a location (like as Tokyo, Osaka, or Kyoto) and invokes the service, the
   system returns chance of rains for the specified area. Additionally, if the request is cached data
   and the cache is still valid data, the response message will be picked up from the cache
   repository.