You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@beehive.apache.org by ek...@apache.org on 2005/08/22 17:25:34 UTC
svn commit: r234506 - in
/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs:
site.xml webservices.xml wsm/wsm_overview.xml
Author: ekoneil
Date: Mon Aug 22 08:25:31 2005
New Revision: 234506
URL: http://svn.apache.org/viewcvs?rev=234506&view=rev
Log:
Remove one-line webservices.xml page which wasn't adding any new content.
BB: self
DRT: build.release pass
Removed:
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/webservices.xml
Modified:
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/site.xml
beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/wsm/wsm_overview.xml
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/site.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/site.xml?rev=234506&r1=234505&r2=234506&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/site.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/site.xml Mon Aug 22 08:25:31 2005
@@ -50,7 +50,6 @@
<wsm_overview label="Web Services Overview" href="wsm/wsm_overview.html"/>
<jws_files label="Java Web Services" href="wsm/wsm_JWSFiles.html"/>
<supported_datatypes label="Supported Data Types" href="wsm/datatypes.html"/>
- <jsr181 label="Web Services (JSR 181)" href="webservices.html"/>
</wsm>
<samples label="Samples">
<sam_index label="Samples" href="samples/index.html"/>
Modified: beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/wsm/wsm_overview.xml
URL: http://svn.apache.org/viewcvs/beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/wsm/wsm_overview.xml?rev=234506&r1=234505&r2=234506&view=diff
==============================================================================
--- beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/wsm/wsm_overview.xml (original)
+++ beehive/trunk/docs/forrest/release/src/documentation/content/xdocs/wsm/wsm_overview.xml Mon Aug 22 08:25:31 2005
@@ -4,90 +4,98 @@
<header>
<title>Web Services Overview</title>
</header>
- <body>
- <section>
- <title>Beehive Web Services Features</title>
- <p><strong>Metadata Annotations</strong></p>
- <p>Beehive web services use Java metadata annotations to simply the web service development process.
- Metadata annotations are easy to learn and use, and offer the developer an especially
- quick way to change the web service implementation. The annotations offer
- implementations of the most common web service features, such as
- (1) conforming to basic SOAP and WSDL standards, (2) separating the public contract
- and the private implementation, and (3) creating asynchronous communication between the
- web service and its clients. The basic idea underlying all Beehive web service development
- is that the developer writes an ordinary Java class, whose functionality is exposed
- as a web service. The manner of exposure is specified by the metadata annotations
- that decorate the class and its methods.</p>
- <p><strong>Standards Based</strong></p>
- <p>Beehive web services are based on
- the <a class="fork" href="http://jcp.org/en/jsr/detail?id=181">JSR 181</a>
- web service standard. JSR 181 sets out the core annotations used to expose
- Java classes as web services.</p>
- <p><strong>No expertise with APIs and Deployment Descriptors Required</strong></p>
- <p>Beehive web services are implemented as ordinary Java classes decorated with
- metadata annotations. The metadata annotations (1) replace the deployment descriptors
- (that would ordinarily be used to configure the Java class)
- and (2) encapsulate the web service APIs (that would ordinarily be used by the developer
- as an implementation resource). The result is a web service implementation that is much
- easier to learn and understand. Instead of keeping multiple Java classes and XML configuration
- files in sync, the developer needs to edit only one file: the annotated Java class.</p>
- <!--<p><strong>Containers</strong></p>
- <p>[todo]</p> -->
- </section>
- <section>
- <title>Web Service Basics</title>
- <p><strong>What Do Web Services Do?</strong></p>
- <p>Web services are servlets that take requests (in the form
- of XML documents) and send back responses (in the form of XML documents).</p>
- <p>Because web services are based on standard technologies (HTTP and XML),
- they make communication possible even
- if the parties are running on different operating systems and are written in different
- languages. For this reason they are an excellent approach for building distributed
- applications that must incorporate diverse systems over a network.</p>
- <p>Web services have the following features:</p>
- <ul>
- <li>The web service's functionality is publicly described in a WSDL file.</li>
- <li>Web services communicate with other applications through XML messages, typically
- in SOAP format.</li>
- <li>Web services generally use a standard network protocol, such as HTTP.</li>
- </ul>
- <section><title>WSDL Files</title>
- <p>The Web Service Description Language (WSDL) is a standard XML format for describing
- web services. A WSDL file describes a particular web service so that other
- software applications can interface with it.</p>
- <p>WSDLs are generally publicly accessible and provide enough
- detail so that potential clients can figure out how to
- operate the service solely from reading the WSDL file. If a
- web service adds two integers and sends back the result to
- the client, the WSDL file will explain how the integers
- should be sent to the web service, and how the resulting
- sum will be returned to the requesting client.</p>
- </section>
- <section><title>XML and SOAP</title>
- <p>Extensible Markup Language (XML) messages provide a common language by which
- different applications can talk to one another over a network. A client sends
- an XML message containing a request to
- the web service, and the web service responds with an XML message containing
- the results of the operation. In most cases these XML messages are formatted
- according to SOAP syntax.</p>
+ <body>
+ <section>
+ <title>Beehive Web Services Features</title>
+ <p><strong>Metadata Annotations</strong></p>
+ <p>Beehive web services use Java metadata annotations to simply the web service development process.
+ Metadata annotations are easy to learn, to use, and offer the developer an especially
+ quick way to build and change a web service implementation. The annotations offer
+ implementations of the most common web service features, such as:
+ </p>
+ <ol>
+ <li>conforming to basic SOAP and WSDL standards</li>
+ <li>separating the public contract and the private implementation</li>
+ <li>creating asynchronous communication between the web service and its clients</li>
+ </ol>
+ <p>
+ The basic idea underlying all Beehive web service development
+ is that a developer writes an ordinary Java class, whose functionality is exposed
+ as a web service. The manner of exposure is specified by the metadata annotations
+ that decorate the class and its methods.</p>
+ <p><strong>Standards Based</strong></p>
+ <p>Beehive web services are based on
+ the <a class="fork" href="http://jcp.org/en/jsr/detail?id=181">JSR 181</a>
+ web service standard. JSR 181 sets out the core annotations used to expose
+ Java classes as web services.</p>
+ <p><strong>No expertise with APIs and Deployment Descriptors Required</strong></p>
+ <p>Beehive web services are implemented as ordinary Java classes decorated with
+ metadata annotations. The metadata annotations (1) replace the deployment descriptors
+ (that would ordinarily be used to configure the Java class)
+ and (2) encapsulate the web service APIs (that would ordinarily be used by the developer
+ as an implementation resource). The result is a web service implementation that is much
+ easier to learn and understand. Instead of keeping multiple Java classes and XML configuration
+ files in sync, the developer needs to edit only one file: the annotated Java class.</p>
+ </section>
+ <section>
+ <title>Web Service Basics</title>
+ <p><strong>What Do Web Services Do?</strong></p>
+ <p>Web services are servlets that take requests (in the form
+ of XML documents) and send back responses (in the form of XML documents).</p>
+ <p>Because web services are based on standard technologies (HTTP and XML),
+ they make communication possible even
+ if the parties are running on different operating systems and are written in different
+ languages. For this reason they are an excellent approach for building distributed
+ applications that must incorporate diverse systems over a network.</p>
+ <p>Web services have the following features:</p>
+ <ul>
+ <li>The web service's functionality is publicly described in a WSDL file.</li>
+ <li>Web services communicate with other applications through XML messages, typically in SOAP format.</li>
+ <li>Web services generally use a standard network protocol, such as HTTP.</li>
+ </ul>
+ <section><title>WSDL Files</title>
+ <p>The Web Service Description Language (WSDL) is a standard XML format for describing
+ web services. A WSDL file describes a particular web service so that other
+ software applications can interface with it.</p>
+ <p>WSDLs are generally publicly accessible and provide enough
+ detail so that potential clients can figure out how to
+ operate the service solely from reading the WSDL file. If a
+ web service adds two integers and sends back the result to
+ the client, the WSDL file will explain how the integers
+ should be sent to the web service, and how the resulting
+ sum will be returned to the requesting client.</p>
+ </section>
+ <section><title>XML and SOAP</title>
+ <p>Extensible Markup Language (XML) messages provide a common language by which
+ different applications can talk to one another over a network. A client sends
+ an XML message containing a request to
+ the web service, and the web service responds with an XML message containing
+ the results of the operation. In most cases these XML messages are formatted
+ according to SOAP syntax.</p>
<p>Simple Object Access Protocol (SOAP) specifies a standard format for applications
- to call each other's methods and pass data to one another. Note that web services
- may communicate with XML messages that are not SOAP-formatted. The types of
- messages supported by a particular web service are delineated in the serviceâs
- WSDL file.</p>
- </section>
- <section><title>Network Protocols</title>
- <p>Web services receive requests and send responses using widely used protocols such
- as HyperText Transfer Protocol (HTTP) and Java Message Service (JMS). A web
- service may support more than one protocol, and different methods on the web
- service may support different protocols. The protocols that a web service
- supports are published in the WSDL file.</p>
- </section>
- </section>
- </body>
+ to call each other's methods and pass data to one another. Note that web services
+ may communicate with XML messages that are not SOAP-formatted. The types of
+ messages supported by a particular web service are delineated in the serviceâs
+ WSDL file.</p>
+ </section>
+ <section><title>Network Protocols</title>
+ <p>Web services receive requests and send responses using widely used protocols such
+ as HyperText Transfer Protocol (HTTP) and Java Message Service (JMS). A web
+ service may support more than one protocol, and different methods on the web
+ service may support different protocols. The protocols that a web service
+ supports are published in the WSDL file.</p>
+ </section>
+ </section>
+ <section>
+ <title>Additional Information</title>
+ <p>Additional information about WSM can be found on the
+ <a class="fork" href="http://wiki.apache.org/beehive/Web_Services">wiki</a>.
+ </p>
+ </section>
+ </body>
<footer>
<legal>Java, J2EE, and JCP are trademarks or registered trademarks of Sun Microsystems, Inc. in the United States and other countries.<br/>
- © 2004, Apache Software Foundation
- </legal>
+ © 2004, Apache Software Foundation
+ </legal>
</footer>
</document>