diff options
Diffstat (limited to 'docs/org.eclipse.jst.ws.doc.user/concepts')
24 files changed, 0 insertions, 2277 deletions
diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita deleted file mode 100644 index 537a28c20..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cjaxrpc" xml:lang="en-us"><?Pub Caret?> -<title>JAX-RPC</title> -<shortdesc>JAX-RPC stands for <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> API for XML-based RPC, also known as -JSR 101. It is a specification that describes <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> Application Programming Interfaces -(APIs) and conventions for building Web services and Web service clients that -use remote procedure calls (RPC) and XML. It standardizes the <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> to -WSDL and WSDL to <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" -trademark="Java">Java</tm> mappings, and provides the core APIs for developing -Web services and Web service clients on the <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> platform. Often used in a distributed -client/server model, an RPC mechanism enables clients to execute procedures -on other systems.</shortdesc> -<conbody> -<p>The current release of JAX-RPC requires the support of SOAP over HTTP for -interoperability purposes. The SOAP specification defines message structure, -encoding rules, and conventions for exchanging information in the RPC programming -model. These calls and responses are transmitted as SOAP messages over HTTP. -In this release, JAX-RPC supports SOAP 1.1 and HTTP 1.1. For more information -on SOAP, refer to <xref href="csoap.dita" scope="local"></xref>.</p> -<p>Although the underlying run-time mechanisms (for example, <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> to -WSDL serialization, WSDL to <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> deserialization, protocol and transport) -are very complex, the API hides this complexity from the application developer. -On the server side, the developer can provide a Service Endpoint Interface -(SEI); alternately an SEI can be created using the Web services wizrds. An -SEI is an interface written in the <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> programming language that specifies -the remote procedures of a Web service. The developer also provides the implementation -of a Web service, in the form of one or more <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> classes that implement methods of the -same signature as those on the SEI. Client programs are also easy to code. -A client creates a proxy, a local object representing the service implementation -and the SEI, and then simply invokes methods on the proxy.</p> -<p>JAX-RPC is highly interoperable: a JAX-RPC client can access a Web service -that is not running on the <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> platform and vice versa. This flexibility -is possible because JAX-RPC uses SOAP over HTTP, and the Web Service Description -Language (WSDL). JAX-RPC was designed to support WS-I.</p> -<p>For more information on JAX-RPC, refer to the <xref format="html" href="http://www.jcp.org/en/jsr/detail?id=101" -scope="external">official JSR 101 specifications</xref>.</p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"></link> -<link href="cwsinwsa.dita"></link> -<link href="cjsr109.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> -<?Pub *0000003863?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html deleted file mode 100644 index e18d4f28c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html +++ /dev/null @@ -1,86 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="JAX-RPC" /> -<meta name="abstract" content="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems." /> -<meta name="description" content="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cjsr109.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cjaxrpc" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>JAX-RPC</title> -</head> -<body id="cjaxrpc"><a name="cjaxrpc"><!-- --></a> - - -<h1 class="topictitle1">JAX-RPC</h1> - - -<div><p>JAX-RPC stands for Java™ API for XML-based RPC, also known as -JSR 101. It is a specification that describes Java Application Programming Interfaces -(APIs) and conventions for building Web services and Web service clients that -use remote procedure calls (RPC) and XML. It standardizes the Java to -WSDL and WSDL to Java mappings, and provides the core APIs for developing -Web services and Web service clients on the Java platform. Often used in a distributed -client/server model, an RPC mechanism enables clients to execute procedures -on other systems.</p> - -<p>The current release of JAX-RPC requires the support of SOAP over HTTP for -interoperability purposes. The SOAP specification defines message structure, -encoding rules, and conventions for exchanging information in the RPC programming -model. These calls and responses are transmitted as SOAP messages over HTTP. -In this release, JAX-RPC supports SOAP 1.1 and HTTP 1.1. For more information -on SOAP, refer to <a href="csoap.html" title="SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns. ">SOAP</a>.</p> - -<p>Although the underlying run-time mechanisms (for example, Java to -WSDL serialization, WSDL to Java deserialization, protocol and transport) -are very complex, the API hides this complexity from the application developer. -On the server side, the developer can provide a Service Endpoint Interface -(SEI); alternately an SEI can be created using the Web services wizrds. An -SEI is an interface written in the Java programming language that specifies -the remote procedures of a Web service. The developer also provides the implementation -of a Web service, in the form of one or more Java classes that implement methods of the -same signature as those on the SEI. Client programs are also easy to code. -A client creates a proxy, a local object representing the service implementation -and the SEI, and then simply invokes methods on the proxy.</p> - -<p>JAX-RPC is highly interoperable: a JAX-RPC client can access a Web service -that is not running on the Java platform and vice versa. This flexibility -is possible because JAX-RPC uses SOAP over HTTP, and the Web Service Description -Language (WSDL). JAX-RPC was designed to support WS-I.</p> - -<p>For more information on JAX-RPC, refer to the <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official JSR 101 specifications</a>.</p> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> -<div><a href="cjsr109.html" title="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate.">JSR 109 and JSR 921- Implementing Enterprise Web services</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita deleted file mode 100644 index 0736ad1d9..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita +++ /dev/null @@ -1,34 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cjsr109" xml:lang="en-us"> -<title>JSR 109 and JSR 921- Implementing Enterprise Web services</title> -<shortdesc>JSR 109 and JSR 921 (Implementing Enterprise Web Services) define -the programming model and run-time architecture to deploy and look up Web -services in the J2EE environment; more specifically, in the Web, EJB, and -Client Application containers. One of its main goals is to ensure vendors' -implementations interoperate.</shortdesc> -<conbody> -<p>JSR 109 and JSR 921 build on top of JAX-RPC to cover the use of JAX-RPC -in a J2EE environment, as well as the implementation and deployment of Web -services to a J2EE application server. JSR 109 and JSR 921 define a set of -XML-based deployment descriptors to standardize Web services and Web service -client deployments in the J2EE environment. These tools support JSR 109 for -J2EE 1.3 and JSR 921 for J2EE 1.4.</p> -<p>For more information, refer to: <xref format="html" href="http://www.jcp.org/en/jsr/detail?id=109" -scope="external">JSR 109, "Implementing Enterprise Web Services</xref> and <xref -href="http://www.jcp.org/en/jsr/detail?id=921" scope="external">JSR 921: Implementing -Enterprise Web Services 1.1</xref>.</p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"></link> -<link href="cwsinwsa.dita"></link> -<link href="cjaxrpc.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html deleted file mode 100644 index 9a13e2c02..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html +++ /dev/null @@ -1,66 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="JSR 109 and JSR 921- Implementing Enterprise Web services" /> -<meta name="abstract" content="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate." /> -<meta name="description" content="JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cjaxrpc.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cjsr109" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>JSR 109 and JSR 921- Implementing Enterprise Web services</title> -</head> -<body id="cjsr109"><a name="cjsr109"><!-- --></a> - - -<h1 class="topictitle1">JSR 109 and JSR 921- Implementing Enterprise Web services</h1> - - -<div><p>JSR 109 and JSR 921 (Implementing Enterprise Web Services) define -the programming model and run-time architecture to deploy and look up Web -services in the J2EE environment; more specifically, in the Web, EJB, and -Client Application containers. One of its main goals is to ensure vendors' -implementations interoperate.</p> - -<p>JSR 109 and JSR 921 build on top of JAX-RPC to cover the use of JAX-RPC -in a J2EE environment, as well as the implementation and deployment of Web -services to a J2EE application server. JSR 109 and JSR 921 define a set of -XML-based deployment descriptors to standardize Web services and Web service -client deployments in the J2EE environment. These tools support JSR 109 for -J2EE 1.3 and JSR 921 for J2EE 1.4.</p> - -<p>For more information, refer to: <a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR 109, "Implementing Enterprise Web Services</a> and <a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR 921: Implementing Enterprise Web Services 1.1</a>.</p> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> -<div><a href="cjaxrpc.html" title="JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems.">JAX-RPC</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita deleted file mode 100644 index 66b53ce09..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita +++ /dev/null @@ -1,102 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="csoap" xml:lang="en-us"> -<title>SOAP</title> -<shortdesc>SOAP (formerly known as Simple Object Access Protocol) is a lightweight -protocol for the exchange of information in a decentralized, distributed environment. -A SOAP message is a transmission of information from a sender to a receiver. -SOAP messages can be combined to perform request/response patterns. </shortdesc> -<conbody> -<p>SOAP is transport independent but is most commonly carried over HTTP in -order to run with the existing Internet infrastructure. SOAP enables -the binding and usage of discovered Web services by defining a message path -for routing messages. SOAP is used to query UDDI for Web services. The workbench -supports SOAP 1.1.</p> -<p>SOAP is an XML-based protocol that defines three parts to every message:</p> -<ul> -<li> <uicontrol>Envelope.</uicontrol> The envelope defines a framework -for describing what is in a message and how to process it. A SOAP message -is an envelope containing zero or more headers and exactly one body. -The envelope is the top element of the XML document, providing a container -for control information, the address of a message, and the message itself. -Headers transport any control information such as quality-of-service attributes. -The body contains the message identification and its parameters. Both -the headers and the body are child elements of the envelope.</li> -<li> <uicontrol>Encoding rules.</uicontrol> The set of encoding rules -expresses instances of application-defined data types. Encoding rules define -a serialization mechanism that can be used to exchange instances of application-defined -data types. SOAP defines a programming language-independent data type scheme -based on XSD plus encoding rules for all data types defined according to this -model. SOAP encoding is not WS-I compliant and thus the Literal use (which -is no encoding) is suggested for interoperable Web services and required for -WS-I compliance.</li> -<li> <uicontrol>Communication styles.</uicontrol> Communications can follow -a remote procedure call (RPC) or message-oriented (Document) format. -These are discussed below.</li> -</ul> -<section><title>Binding styles</title><p>SOAP supports two different communication -styles:</p><lq> <p> <uicontrol>Remote procedure call (RPC):</uicontrol> -Invocation of an operation returning a result. Typically used with SOAP encoding, -which is not WS-I compliant.</p><p> <uicontrol>Document Style:</uicontrol> -Also known as document-oriented or message-oriented style. This style -provides a lower layer of abstraction, and requires more programming work.</p> </lq></section> -<section><title>Encoding styles</title><p>In distributed computing environments, -encoding styles define how data values defined in the application can be translated -to and from a particular protocol format. The translation process is -know as serialization and deserialization.</p><p>The SOAP specification defines -the SOAP encoding style:</p><lq> <p> <uicontrol>SOAP encoding:</uicontrol> -The SOAP encoding style allows you to serialize/deserialize values of data -types from the SOAP data model. This encoding style is defined in the -SOAP 1.1 standard, and is not WS-I compliant.</p> </lq><p>WSDL defines the -Literal XML encoding style:</p><lq> <p> <uicontrol>Literal XML:</uicontrol> -Literal refers to the fact that the document should be read as-is, or unencoded. -The document is serialized as XMI, meaning that the message XML complies with -the Schema in the WSDL. When using Literal encoding, each message part references -a concrete schema definition. Literal encoding is WS-I compliant.</p> </lq></section> -<section><title>Data model</title><p>The purpose of the SOAP data model is -to provide a language-independent abstraction for data types used by common -programming language types. It consists of:</p><ul> -<li> <uicontrol>Simple XSD types.</uicontrol> For example int, string, -and date.</li> -<li> <uicontrol>Compound types.</uicontrol> There are two kinds of compound -types, <varname>structs</varname> and <varname>arrays</varname>. Structs -are named aggregate types in which each element has a unique name or XML tag. -Arrays have elements that are identified by position, not by name.</li> -</ul><p>All elements and identifiers comprising the SOAP data model are defined -in the namespace URI. The SOAP standard defines the rules for how data -types can be constructed. A project specific XML schema must define the actual -data types. The elements of the SOAP specification are defined in <xref format="html" -href="http://schemas.xmlsoap.org/soap/envelope/" scope="external">http://schemas.xmlsoap.org/soap/envelope/</xref> and - <xref format="html" href="http://schemas.xmlsoap.org/soap/encoding/" scope="external">http://schemas.xmlsoap.org/soap/encoding/</xref></p></section> -<section><title>SOAP implementations</title><p>Different implementations of -the SOAP protocol are available today. For example, the Apache Foundation -provides Apache SOAP, which grew out of an <tm tmclass="ibm" tmowner="IBM Corporation" -tmtype="reg" trademark="IBM">IBM</tm> project called SOAP4J, as well as Apache -Axis and the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> <tm -tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="WebSphere">WebSphere</tm> run-time -environment. The provided Web services tools support Apache SOAP 2.3, Axis -1.0, and <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> <tm -tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="WebSphere">WebSphere</tm> implementations.</p></section> -<section><title>Mappings</title><p>A mapping defines an association between -a qualified XML element name, a <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> class name, and an encoding style. -The mapping specifies how, under the given encoding, an incoming XML element -with a fully qualified name is converted to a <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> class and vice versa.</p><p>For more -information on Apache SOAP, refer to <xref format="html" href="http://xml.apache.org/soap" -scope="external">xml.apache.org/soap</xref> For more information on -SOAP refer to <xref format="html" href="http://www.w3.org/TR/SOAP" scope="external">www.w3.org/TR/SOAP</xref> </p></section> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"><linktext>Web services overview</linktext></link> -<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> -</link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html b/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html deleted file mode 100644 index a93b36250..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html +++ /dev/null @@ -1,156 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="SOAP" /> -<meta name="abstract" content="SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns." /> -<meta name="description" content="SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="csoap" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>SOAP</title> -</head> -<body id="csoap"><a name="csoap"><!-- --></a> - - -<h1 class="topictitle1">SOAP</h1> - - -<div><p>SOAP (formerly known as Simple Object Access Protocol) is a lightweight -protocol for the exchange of information in a decentralized, distributed environment. -A SOAP message is a transmission of information from a sender to a receiver. -SOAP messages can be combined to perform request/response patterns. </p> - -<p>SOAP is transport independent but is most commonly carried over HTTP in -order to run with the existing Internet infrastructure. SOAP enables -the binding and usage of discovered Web services by defining a message path -for routing messages. SOAP is used to query UDDI for Web services. The workbench -supports SOAP 1.1.</p> - -<p>SOAP is an XML-based protocol that defines three parts to every message:</p> - -<ul> -<li> <span class="uicontrol">Envelope.</span> The envelope defines a framework -for describing what is in a message and how to process it. A SOAP message -is an envelope containing zero or more headers and exactly one body. -The envelope is the top element of the XML document, providing a container -for control information, the address of a message, and the message itself. -Headers transport any control information such as quality-of-service attributes. -The body contains the message identification and its parameters. Both -the headers and the body are child elements of the envelope.</li> - -<li> <span class="uicontrol">Encoding rules.</span> The set of encoding rules -expresses instances of application-defined data types. Encoding rules define -a serialization mechanism that can be used to exchange instances of application-defined -data types. SOAP defines a programming language-independent data type scheme -based on XSD plus encoding rules for all data types defined according to this -model. SOAP encoding is not WS-I compliant and thus the Literal use (which -is no encoding) is suggested for interoperable Web services and required for -WS-I compliance.</li> - -<li> <span class="uicontrol">Communication styles.</span> Communications can follow -a remote procedure call (RPC) or message-oriented (Document) format. -These are discussed below.</li> - -</ul> - -<div class="section"><h4 class="sectiontitle">Binding styles</h4><p>SOAP supports two different communication -styles:</p> -<blockquote> <p> <span class="uicontrol">Remote procedure call (RPC):</span> -Invocation of an operation returning a result. Typically used with SOAP encoding, -which is not WS-I compliant.</p> -<p> <span class="uicontrol">Document Style:</span> -Also known as document-oriented or message-oriented style. This style -provides a lower layer of abstraction, and requires more programming work.</p> - </blockquote> -</div> - -<div class="section"><h4 class="sectiontitle">Encoding styles</h4><p>In distributed computing environments, -encoding styles define how data values defined in the application can be translated -to and from a particular protocol format. The translation process is -know as serialization and deserialization.</p> -<p>The SOAP specification defines -the SOAP encoding style:</p> -<blockquote> <p> <span class="uicontrol">SOAP encoding:</span> -The SOAP encoding style allows you to serialize/deserialize values of data -types from the SOAP data model. This encoding style is defined in the -SOAP 1.1 standard, and is not WS-I compliant.</p> - </blockquote> -<p>WSDL defines the -Literal XML encoding style:</p> -<blockquote> <p> <span class="uicontrol">Literal XML:</span> -Literal refers to the fact that the document should be read as-is, or unencoded. -The document is serialized as XMI, meaning that the message XML complies with -the Schema in the WSDL. When using Literal encoding, each message part references -a concrete schema definition. Literal encoding is WS-I compliant.</p> - </blockquote> -</div> - -<div class="section"><h4 class="sectiontitle">Data model</h4><p>The purpose of the SOAP data model is -to provide a language-independent abstraction for data types used by common -programming language types. It consists of:</p> -<ul> -<li> <span class="uicontrol">Simple XSD types.</span> For example int, string, -and date.</li> - -<li> <span class="uicontrol">Compound types.</span> There are two kinds of compound -types, <var class="varname">structs</var> and <var class="varname">arrays</var>. Structs -are named aggregate types in which each element has a unique name or XML tag. -Arrays have elements that are identified by position, not by name.</li> - -</ul> -<p>All elements and identifiers comprising the SOAP data model are defined -in the namespace URI. The SOAP standard defines the rules for how data -types can be constructed. A project specific XML schema must define the actual -data types. The elements of the SOAP specification are defined in <a href="http://schemas.xmlsoap.org/soap/envelope/" target="_blank">http://schemas.xmlsoap.org/soap/envelope/</a> and - <a href="http://schemas.xmlsoap.org/soap/encoding/" target="_blank">http://schemas.xmlsoap.org/soap/encoding/</a></p> -</div> - -<div class="section"><h4 class="sectiontitle">SOAP implementations</h4><p>Different implementations of -the SOAP protocol are available today. For example, the Apache Foundation -provides Apache SOAP, which grew out of an IBM<sup>®</sup> project called SOAP4J, as well as Apache -Axis and the IBM WebSphere<sup>®</sup> run-time -environment. The provided Web services tools support Apache SOAP 2.3, Axis -1.0, and IBM WebSphere implementations.</p> -</div> - -<div class="section"><h4 class="sectiontitle">Mappings</h4><p>A mapping defines an association between -a qualified XML element name, a Java™ class name, and an encoding style. -The mapping specifies how, under the given encoding, an incoming XML element -with a fully qualified name is converted to a Java class and vice versa.</p> -<p>For more -information on Apache SOAP, refer to <a href="http://xml.apache.org/soap" target="_blank">xml.apache.org/soap</a> For more information on -SOAP refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a> </p> -</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita deleted file mode 100644 index b7e681fbd..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita +++ /dev/null @@ -1,88 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cws" xml:lang="en-us"> -<title>Web services overview</title> -<shortdesc>A Web service is a set of related application functions that can -be programmatically invoked over the Internet. Businesses can dynamically -mix and match Web services to perform complex transactions with minimal programming. -Web services allow buyers and sellers all over the world to discover each -other, connect dynamically, and execute transactions in real time with minimal -human interaction.</shortdesc> -<conbody> -<p>Web services are self-contained, self-describing modular applications that -can be published, located, and invoked across the Web.</p> -<lq> <p> <uicontrol>Web services are self-contained.</uicontrol> On the client -side, no additional software is required. A programming language with -XML and HTTP client support is enough to get you started. On the server -side, a Web server and servlet engine are required. The client and server -can be implemented in different environments. It is possible to Web -service enable an existing application without writing a single line of code.</p> <p> <uicontrol>Web -services are self-describing.</uicontrol> The client and server need to recognize -only the format and content of request and response messages. The definition -of the message format travels with the message; no external metadata repositories -or code generation tools are required.</p> <p> <uicontrol>Web services are -modular.</uicontrol> Simple Web services can be aggregated to form more complex -Web services either by using workflow techniques or by calling lower layer -Web services from a Web service implementation.</p><p><uicontrol>Web Services -are platform independent.</uicontrol> Web services are based on a concise -set of open, XML-based standards designed to promote interoperability between -a Web service and clients across a variety of computing platforms and programming -languages.</p> </lq> -<p>Web services might be anything, for example, theatre review articles, weather -reports, credit checks, stock quotations, travel advisories, or airline travel -reservation processes. Each of these self-contained business services is an -application that can easily integrate with other services, from the same or -different companies, to create a complete business process. This interoperability -allows businesses to dynamically publish, discover, and bind a range of Web -services through the Internet.</p> -<section><title>Categories of Web services</title><p>Web services can be grouped -into three categories:</p><lq> <p> <uicontrol>Business information.</uicontrol> A -business shares information with consumers or other businesses. In this case, -the business is using Web services to expand its scope. Examples of business -informational Web services are news streams, weather reports, or stock quotations.</p> <p> <uicontrol>Business -integration.</uicontrol> A business provides transactional, "for fee" services -to its customers. In this case, the business becomes part of a global network -of value-added suppliers that can be used to conduct commerce. Examples of -business integration Web services include bid and auction e-marketplaces, -reservation systems, and credit checking.</p> <p> <uicontrol>Business process -externalization.</uicontrol> A business differentiates itself from its competition -through the creation of a global value chain. In this case, the business uses -Web services to dynamically integrate its processes. An example of business -process externalization Web services is the associations between different -companies to combine manufacturing, assembly, wholesale distribution, and -retail sales of a particular product.</p> </lq></section> -<section><title>Service roles and interactions</title><p>A network component -in a Web Services architecture can play one or more fundamental roles: service -provider, service broker, and service client.</p><ul> -<li>Service providers create and deploy their Web services and can publish -the availability of their WSDL-described services through a service registry, -such as a UDDI Business Registry.</li> -<li>Service brokers register and categorize published services and provide -search services. For example, UDDI acts as a service broker for WSDL-described -Web services.</li> -<li>Service clients use broker services such as the UDDI Business Registry -to discover a needed WSDL-described service and then bind to and call the -service provider.</li> -</ul><p>Binding involves establishing all environmental prerequisites that -are necessary to successfully complete the services. Examples of environmental -prerequisites include security, transaction monitoring, and HTTP availability. -The relationships between these roles are described in Figure 1.</p><p>Figure -1. Service roles and interactions.</p><p> <image alt="Figure 1 illustrates the interactions between the service broker, service provider, and service requestor." -href="../images/roles.gif"></image> </p><p>For more information on Web services, -refer to <xref format="html" href="http://www.ibm.com/developerworks/webservices" -scope="external">www..com/developerworks/webservices</xref></p></section> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> -</link> -<link href="cwsstandards.dita" scope="local"><linktext>Web services standards</linktext> -</link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html deleted file mode 100644 index 9718d7ea1..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html +++ /dev/null @@ -1,140 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web services overview" /> -<meta name="abstract" content="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction." /> -<meta name="description" content="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cws" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Web services overview</title> -</head> -<body id="cws"><a name="cws"><!-- --></a> - - -<h1 class="topictitle1">Web services overview</h1> - - -<div><p>A Web service is a set of related application functions that can -be programmatically invoked over the Internet. Businesses can dynamically -mix and match Web services to perform complex transactions with minimal programming. -Web services allow buyers and sellers all over the world to discover each -other, connect dynamically, and execute transactions in real time with minimal -human interaction.</p> - -<p>Web services are self-contained, self-describing modular applications that -can be published, located, and invoked across the Web.</p> - -<blockquote> <p> <span class="uicontrol">Web services are self-contained.</span> On the client -side, no additional software is required. A programming language with -XML and HTTP client support is enough to get you started. On the server -side, a Web server and servlet engine are required. The client and server -can be implemented in different environments. It is possible to Web -service enable an existing application without writing a single line of code.</p> - <p> <span class="uicontrol">Web -services are self-describing.</span> The client and server need to recognize -only the format and content of request and response messages. The definition -of the message format travels with the message; no external metadata repositories -or code generation tools are required.</p> - <p> <span class="uicontrol">Web services are -modular.</span> Simple Web services can be aggregated to form more complex -Web services either by using workflow techniques or by calling lower layer -Web services from a Web service implementation.</p> -<p><span class="uicontrol">Web Services -are platform independent.</span> Web services are based on a concise -set of open, XML-based standards designed to promote interoperability between -a Web service and clients across a variety of computing platforms and programming -languages.</p> - </blockquote> - -<p>Web services might be anything, for example, theatre review articles, weather -reports, credit checks, stock quotations, travel advisories, or airline travel -reservation processes. Each of these self-contained business services is an -application that can easily integrate with other services, from the same or -different companies, to create a complete business process. This interoperability -allows businesses to dynamically publish, discover, and bind a range of Web -services through the Internet.</p> - -<div class="section"><h4 class="sectiontitle">Categories of Web services</h4><p>Web services can be grouped -into three categories:</p> -<blockquote> <p> <span class="uicontrol">Business information.</span> A -business shares information with consumers or other businesses. In this case, -the business is using Web services to expand its scope. Examples of business -informational Web services are news streams, weather reports, or stock quotations.</p> - <p> <span class="uicontrol">Business -integration.</span> A business provides transactional, "for fee" services -to its customers. In this case, the business becomes part of a global network -of value-added suppliers that can be used to conduct commerce. Examples of -business integration Web services include bid and auction e-marketplaces, -reservation systems, and credit checking.</p> - <p> <span class="uicontrol">Business process -externalization.</span> A business differentiates itself from its competition -through the creation of a global value chain. In this case, the business uses -Web services to dynamically integrate its processes. An example of business -process externalization Web services is the associations between different -companies to combine manufacturing, assembly, wholesale distribution, and -retail sales of a particular product.</p> - </blockquote> -</div> - -<div class="section"><h4 class="sectiontitle">Service roles and interactions</h4><p>A network component -in a Web Services architecture can play one or more fundamental roles: service -provider, service broker, and service client.</p> -<ul> -<li>Service providers create and deploy their Web services and can publish -the availability of their WSDL-described services through a service registry, -such as a UDDI Business Registry.</li> - -<li>Service brokers register and categorize published services and provide -search services. For example, UDDI acts as a service broker for WSDL-described -Web services.</li> - -<li>Service clients use broker services such as the UDDI Business Registry -to discover a needed WSDL-described service and then bind to and call the -service provider.</li> - -</ul> -<p>Binding involves establishing all environmental prerequisites that -are necessary to successfully complete the services. Examples of environmental -prerequisites include security, transaction monitoring, and HTTP availability. -The relationships between these roles are described in Figure 1.</p> -<p>Figure -1. Service roles and interactions.</p> -<p> <img src="../images/roles.gif" alt="Figure 1 illustrates the interactions between the service broker, service provider, and service requestor." /> </p> -<p>For more information on Web services, -refer to <a href="http://www.ibm.com/developerworks/webservices" target="_blank">www..com/developerworks/webservices</a></p> -</div> - -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../concepts/cwsstandards.html">Web services standards</a></strong><br /> -One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.</li> -</ul> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> -<div><a href="cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita deleted file mode 100644 index a7a19ea43..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita +++ /dev/null @@ -1,33 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="creatingbottom-upwebservices" xml:lang="en-us"><?Pub Caret?> -<title>Creating bottom-up Web services</title> -<shortdesc>Web services can be created using two methods: top-down development -and bottom-up development. Bottom-up Web services development involves creating -a Web service from a <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> bean or enterprise bean.</shortdesc> -<conbody> -<p>Although bottom-up Web service development may be faster and easier, especially -if you are new to Web services, the top-down approach is the recommended way -of creating a Web service.</p> -<p>When creating a Web service using a bottom-up approach, first you create -a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> bean -or EJB bean and then use the Web services wizard to create the WSDL file and -Web service.</p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"><linktext>Web services overview</linktext></link> -<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> -</link> -<link href="cwstopdown.dita" scope="local"><linktext>Creating top-down Web -services</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> -<?Pub *0000001612?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html deleted file mode 100644 index cac91b99f..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html +++ /dev/null @@ -1,65 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Creating bottom-up Web services" /> -<meta name="abstract" content="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean." /> -<meta name="description" content="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean." /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cwstopdown.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="creatingbottom-upwebservices" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Creating bottom-up Web services</title> -</head> -<body id="creatingbottom-upwebservices"><a name="creatingbottom-upwebservices"><!-- --></a> - - -<h1 class="topictitle1">Creating bottom-up Web services</h1> - - -<div><p>Web services can be created using two methods: top-down development -and bottom-up development. Bottom-up Web services development involves creating -a Web service from a Java™ bean or enterprise bean.</p> - -<p>Although bottom-up Web service development may be faster and easier, especially -if you are new to Web services, the top-down approach is the recommended way -of creating a Web service.</p> - -<p>When creating a Web service using a bottom-up approach, first you create -a Java bean -or EJB bean and then use the Web services wizard to create the WSDL file and -Web service.</p> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB).">Developing Web services</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> -<div><a href="cwstopdown.html" title="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file.">Creating top-down Web -services</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita deleted file mode 100644 index 750fc1022..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita +++ /dev/null @@ -1,70 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<?Pub Inc?> -<concept id="cwsdl" xml:lang="en-us"><?Pub Caret?> -<title>Web Services Description Language (WSDL)</title> -<shortdesc>Web Services Description Language (WSDL) is a standard specification -for describing networked, XML-based services. It provides a simple way for -service providers to describe the basic format of requests to their systems -regardless of the underlying run-time implementation.</shortdesc> -<conbody> -<p>WSDL defines an XML format for describing network services as a set of - <varname>endpoints</varname> that operate on messages that contain either -document-oriented or procedure-oriented information. The operations and messages -are first described abstractly and then bound to a concrete network protocol -and message format in order to define an endpoint. Related concrete endpoints -are combined into abstract endpoints (services). WSDL is extensible to allow -description of endpoints and their messages, regardless of which message formats -or network protocols are used to communicate. This means that interfaces are -defined abstractly using XML schema and then bound to concrete representations -that are appropriate for the protocol.</p> -<p>WSDL allows a service provider to specify the following characteristics -of a Web service:</p> -<ul> -<li>The name of the Web service and addressing information</li> -<li>The protocol and encoding style to be used when accessing the public operations -of the Web service</li> -<li>The type information such as operations, parameters, and data types comprising -the interface of the Web service</li> -</ul> -<p>WSDL documents allow developers to expose their applications as network-accessible -services on the Internet. Through UDDI and WSIL, other applications can discover -WSDL documents and bind with them to execute transactions or perform other -business processes.</p> -<p>This development platform supports and encourages the development and use -of WS-I compliant WSDL. Business service providers can deploy <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> beans -and enterprise beans as a Web service and generate a WSDL document that describes -the service. They can also generate <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> and enterprise bean skeletons from -an existing WSDL file. A business service client can generate a <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> proxy -from a WSDL document, thereby providing an easy-to-use <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> interface -to the Web service. The <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> interface hides the network communications -details from the client enabling the business service provider to focus on -business and process portions of the application.</p> -<p>In addition to providing tools to create Web services, the workbench provides -a WSDL editor that allows you to create WSDL files using a graphical interface, -a WSDL validator that ensures that your WSDL file is semantically correct -and optionally checks for WS-I compliance, and the Web Services Explorer which -allows you to dynamically test Web services without requiring you to generate -a proxy.</p> -<p>The workbench supports WSDL 1.1. For more information on the WSDL specification, -refer to <xref format="html" href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"><linktext>Web services overview</linktext></link> -<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> -</link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> -<?Pub *0000004138?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html deleted file mode 100644 index ad54b5156..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html +++ /dev/null @@ -1,110 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web Services Description Language (WSDL)" /> -<meta name="abstract" content="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation." /> -<meta name="description" content="Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="../ref/rwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwsdl" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Web Services Description Language (WSDL)</title> -</head> -<body id="cwsdl"><a name="cwsdl"><!-- --></a> - - -<h1 class="topictitle1">Web Services Description Language (WSDL)</h1> - - -<div><p>Web Services Description Language (WSDL) is a standard specification -for describing networked, XML-based services. It provides a simple way for -service providers to describe the basic format of requests to their systems -regardless of the underlying run-time implementation.</p> - -<p>WSDL defines an XML format for describing network services as a set of - <var class="varname">endpoints</var> that operate on messages that contain either -document-oriented or procedure-oriented information. The operations and messages -are first described abstractly and then bound to a concrete network protocol -and message format in order to define an endpoint. Related concrete endpoints -are combined into abstract endpoints (services). WSDL is extensible to allow -description of endpoints and their messages, regardless of which message formats -or network protocols are used to communicate. This means that interfaces are -defined abstractly using XML schema and then bound to concrete representations -that are appropriate for the protocol.</p> - -<p>WSDL allows a service provider to specify the following characteristics -of a Web service:</p> - -<ul> -<li>The name of the Web service and addressing information</li> - -<li>The protocol and encoding style to be used when accessing the public operations -of the Web service</li> - -<li>The type information such as operations, parameters, and data types comprising -the interface of the Web service</li> - -</ul> - -<p>WSDL documents allow developers to expose their applications as network-accessible -services on the Internet. Through UDDI and WSIL, other applications can discover -WSDL documents and bind with them to execute transactions or perform other -business processes.</p> - -<p>This development platform supports and encourages the development and use -of WS-I compliant WSDL. Business service providers can deploy Java™ beans -and enterprise beans as a Web service and generate a WSDL document that describes -the service. They can also generate Java and enterprise bean skeletons from -an existing WSDL file. A business service client can generate a Java proxy -from a WSDL document, thereby providing an easy-to-use Java interface -to the Web service. The Java interface hides the network communications -details from the client enabling the business service provider to focus on -business and process portions of the application.</p> - -<p>In addition to providing tools to create Web services, the workbench provides -a WSDL editor that allows you to create WSDL files using a graphical interface, -a WSDL validator that ensures that your WSDL file is semantically correct -and optionally checks for WS-I compliance, and the Web Services Explorer which -allows you to dynamically test Web services without requiring you to generate -a proxy.</p> - -<p>The workbench supports WSDL 1.1. For more information on the WSDL specification, -refer to <a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> - -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../ref/rwsdl.html">Web Services Description Language (WSDL) reference</a></strong><br /> -A WSDL document defines services as collections of network endpoints, or ports. In WSDL, the abstract definition of endpoints and messages is separated from their concrete network deployment or data format bindings. This allows the reuse of abstract definitions: messages, which are abstract descriptions of the data being exchanged, and port types which are abstract collections of operations.</li> -</ul> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita deleted file mode 100644 index f9bf93009..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita +++ /dev/null @@ -1,79 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cwsil" xml:lang="en-us"> -<title>Web Services Inspection Language (WSIL)</title> -<shortdesc>Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -When you discover Web services with UDDI, you go to a centralized registry. -WSIL is an alternative approach to Web service discovery. WSIL allows -you to go directly to the service provider and ask for the services it provides.</shortdesc> -<conbody> -<p><tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" trademark="IBM">IBM</tm> and -Microsoft's proposal for the WSIL specification is designed around an XML-based -model for building an aggregation of references to existing Web service descriptions, -that are exposed using standard Web server technology.</p> -<p>WSIL provides a distributed service discovery method that supplies references -to service descriptions at the service provider's point-of-offering, by specifying -how to inspect a Web site for available Web services. The WSIL specification -defines the locations on a Web site where you can look for Web service descriptions.</p> -<p>Since WSIL focuses on distributed service discovery, the WSIL specification -complements UDDI by facilitating the discovery of services that are available -on Web sites that may not be listed yet in a UDDI registry. A separate topic -in this documentation discusses the <xref href="cwsilud.dita">Relationship -between UDDI and WSIL</xref>.</p> -<p>The WSIL specification does not define a service description language. -WSIL documents provide a method for aggregating different types of service -descriptions. Within a WSIL document, a single service can have more -than one reference to a service description. For example, a single Web -service might be referenced twice in a WSIL document: once directly via its -WSDL, and again via its businessService entry in a UDDI registry. References -to these two service descriptions should be put into a WSIL document. -If multiple references are available, it is beneficial to put all of them -in the WSIL document so that the application that uses the document can select -the type of service description that is compatible with and preferred by that -application.</p> -<p>The WSIL specification serves two primary functions:</p> -<ul> -<li>WSIL defines an XML format for listing references to existing service -descriptions. These service descriptions can be defined in any format, such -as WSDL, UDDI, or plain HTML. A WSIL document is generally made available -at the point-of-offering for the services that are referenced within the document. -A WSIL document can contain a list of references to service descriptions, -as well as references to other WSIL documents. <p>The ability to link a WSIL -document to one or more different WSIL documents allows you to manage service -description references by grouping them into different documents and to build -a hierarchy of WSIL documents. For example, separate WSIL documents -can be created for different categories of services, and one primary WSIL -document can link all of them together.</p></li> -<li>WSIL defines a set of conventions so that it is easy to locate other WSIL -documents. The WSIL specification does not limit the type of service descriptions -that can be referenced. The WSIL specification defines a set of standard -extensibility elements for both WSDL and UDDI. The WSIL specification -is the definition of locations where you can access WSIL documents.</li> -<li> Two conventions make the location and retrieval of WSIL documents easy: <ul> -<li> <uicontrol>Fixed-name WSIL documents.</uicontrol> The fixed name for -WSIL documents is inspection.wsil. The inspection.wsil file is placed -at common entry points for a Web site. For example, if the common entry -point is http://entrypoint.com then the location of the WSIL document would -be http://entrypoint.com/inspection.wsil</li> -<li> <uicontrol>Linked WSIL documents.</uicontrol> References to WSIL documents -can also appear within different content documents, such as HTML pages.</li> -</ul> </li> -</ul> -<p>For more information on the Web Services Inspection Language specification, -refer to <xref href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" -scope="external"> www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</xref></p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"><linktext>Web services overview</linktext></link> -<link href="cwsinwsa.dita"><linktext>Tools for Web services development</linktext> -</link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html deleted file mode 100644 index 0f2abab54..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html +++ /dev/null @@ -1,128 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web Services Inspection Language (WSIL)" /> -<meta name="abstract" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides." /> -<meta name="description" content="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsstandards.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsilud.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwsil" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Web Services Inspection Language (WSIL)</title> -</head> -<body id="cwsil"><a name="cwsil"><!-- --></a> - - -<h1 class="topictitle1">Web Services Inspection Language (WSIL)</h1> - - -<div><p>Web Services Inspection Language (WSIL) is a service discovery -mechanism that is an alternative to UDDI as well as complementary to UDDI. -When you discover Web services with UDDI, you go to a centralized registry. -WSIL is an alternative approach to Web service discovery. WSIL allows -you to go directly to the service provider and ask for the services it provides.</p> - -<p>IBM<sup>®</sup> and -Microsoft's proposal for the WSIL specification is designed around an XML-based -model for building an aggregation of references to existing Web service descriptions, -that are exposed using standard Web server technology.</p> - -<p>WSIL provides a distributed service discovery method that supplies references -to service descriptions at the service provider's point-of-offering, by specifying -how to inspect a Web site for available Web services. The WSIL specification -defines the locations on a Web site where you can look for Web service descriptions.</p> - -<p>Since WSIL focuses on distributed service discovery, the WSIL specification -complements UDDI by facilitating the discovery of services that are available -on Web sites that may not be listed yet in a UDDI registry. A separate topic -in this documentation discusses the <a href="cwsilud.html">Relationship between UDDI and WSIL</a>.</p> - -<p>The WSIL specification does not define a service description language. -WSIL documents provide a method for aggregating different types of service -descriptions. Within a WSIL document, a single service can have more -than one reference to a service description. For example, a single Web -service might be referenced twice in a WSIL document: once directly via its -WSDL, and again via its businessService entry in a UDDI registry. References -to these two service descriptions should be put into a WSIL document. -If multiple references are available, it is beneficial to put all of them -in the WSIL document so that the application that uses the document can select -the type of service description that is compatible with and preferred by that -application.</p> - -<p>The WSIL specification serves two primary functions:</p> - -<ul> -<li>WSIL defines an XML format for listing references to existing service -descriptions. These service descriptions can be defined in any format, such -as WSDL, UDDI, or plain HTML. A WSIL document is generally made available -at the point-of-offering for the services that are referenced within the document. -A WSIL document can contain a list of references to service descriptions, -as well as references to other WSIL documents. <p>The ability to link a WSIL -document to one or more different WSIL documents allows you to manage service -description references by grouping them into different documents and to build -a hierarchy of WSIL documents. For example, separate WSIL documents -can be created for different categories of services, and one primary WSIL -document can link all of them together.</p> -</li> - -<li>WSIL defines a set of conventions so that it is easy to locate other WSIL -documents. The WSIL specification does not limit the type of service descriptions -that can be referenced. The WSIL specification defines a set of standard -extensibility elements for both WSDL and UDDI. The WSIL specification -is the definition of locations where you can access WSIL documents.</li> - -<li> Two conventions make the location and retrieval of WSIL documents easy: <ul> -<li> <span class="uicontrol">Fixed-name WSIL documents.</span> The fixed name for -WSIL documents is inspection.wsil. The inspection.wsil file is placed -at common entry points for a Web site. For example, if the common entry -point is http://entrypoint.com then the location of the WSIL document would -be http://entrypoint.com/inspection.wsil</li> - -<li> <span class="uicontrol">Linked WSIL documents.</span> References to WSIL documents -can also appear within different content documents, such as HTML pages.</li> - -</ul> - </li> - -</ul> - -<p>For more information on the Web Services Inspection Language specification, -refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank">www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a></p> - -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../concepts/cwsilud.html">Relationship between UDDI and WSIL</a></strong><br /> -The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI.</li> -</ul> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsstandards.html" title="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards.">Web services standards</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita deleted file mode 100644 index 477eb1f54..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita +++ /dev/null @@ -1,68 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cwsilud" xml:lang="en-us"> -<title>Relationship between UDDI and WSIL</title> -<shortdesc>The Web Services Inspection Language (WSIL) and the Universal Description, -Discovery, and Integration (UDDI) specification both address issues related -to Web service discovery. However, each specification takes a different -approach to the discovery of Web services. The two specifications can -be used separately or jointly; searching with WSIL can result in finding items -in UDDI.</shortdesc> -<conbody> -<p>The UDDI specification addresses Web service discovery through the use -of a centralized model. One or more repositories are created to house -information about businesses and the services they offer. Requests and -updates pertaining to the service and business related information are issued -directly against the repositories. In addition, UDDI prescribes a specific -format for a portion of the stored description information and, to facilitate -advanced (focused) searching, assumes that other description information will -be stored and registered within the system as well.</p> -<p>UDDI systems facilitate focused discovery patterns since these systems -are based on organized repositories that provide advanced searching capabilities. -This helps requestors locate potential communication partners. In order -to provide advanced functionality, however, UDDI requires the deployment and -maintenance of a certain amount of infrastructure, thus increasing the cost -of operation. In addition, unless the service descriptions are stored -only within UDDI, there is a cost associated with keeping the different versions -synchronized.</p> -<p>The WSIL specification relies on a completely distributed model for providing -service-related information. The service descriptions can be stored -at any location, and requests to retrieve the information are generally made -directly to the entities that are offering the services. The WSIL specification -does not stipulate any particular format for the service information. -It relies on other standards, including UDDI, to define the description formats. -The WSIL specification also relies on existing Web technologies and infrastructure -to provide mechanisms for publishing and retrieving its documents.</p> -<p>WSIL provides the ability to disseminate service-related information through -existing protocols directly from the point at which the service is being offered. -This enables focused discovery to be performed on a single target; however, -because of its decentralized and distributed model, WSIL is not a good mechanism -for executing focused discovery if the communication partner is unknown.</p> -<p>The UDDI and WSIL specifications should be viewed as complementary technologies -to be used either together or separately depending on the situation. -For example, a UDDI repository could be populated based on the results found -when performing a search for WSIL documents. Likewise, a UDDI repository -may itself be discovered when a requester retrieves a WSIL document that references -an entry in the repository. In environments where the advanced functionality -afforded by UDDI is not required and where constraints do not allow for its -deployment, the WSIL mechanism may provide all of the capabilities that are -needed. In situations where data needs to be centrally managed, a UDDI -solution alone may provide the best fit. The UDDI and WSIL specifications -should not be viewed as mutually exclusive.</p> -<note>Both UDDI and WSIL contain only references to WSDL - they do not contain -the WSDL documents themselves.</note> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"></link> -<link href="cwsinwsa.dita"></link> -<link href="cwsil.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><?Pub Caret?><linktext> Developing -Web services</linktext></link> -</linklist> -</related-links> -</concept> -<?Pub *0000004226?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html deleted file mode 100644 index f471b5ba4..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html +++ /dev/null @@ -1,106 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Relationship between UDDI and WSIL" /> -<meta name="abstract" content="The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI." /> -<meta name="description" content="The Web Services Inspection Language (WSIL) and the Universal Description, Discovery, and Integration (UDDI) specification both address issues related to Web service discovery. However, each specification takes a different approach to the discovery of Web services. The two specifications can be used separately or jointly; searching with WSIL can result in finding items in UDDI." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsil.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsil.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwsilud" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Relationship between UDDI and WSIL</title> -</head> -<body id="cwsilud"><a name="cwsilud"><!-- --></a> - - -<h1 class="topictitle1">Relationship between UDDI and WSIL</h1> - - -<div><p>The Web Services Inspection Language (WSIL) and the Universal Description, -Discovery, and Integration (UDDI) specification both address issues related -to Web service discovery. However, each specification takes a different -approach to the discovery of Web services. The two specifications can -be used separately or jointly; searching with WSIL can result in finding items -in UDDI.</p> - -<p>The UDDI specification addresses Web service discovery through the use -of a centralized model. One or more repositories are created to house -information about businesses and the services they offer. Requests and -updates pertaining to the service and business related information are issued -directly against the repositories. In addition, UDDI prescribes a specific -format for a portion of the stored description information and, to facilitate -advanced (focused) searching, assumes that other description information will -be stored and registered within the system as well.</p> - -<p>UDDI systems facilitate focused discovery patterns since these systems -are based on organized repositories that provide advanced searching capabilities. -This helps requestors locate potential communication partners. In order -to provide advanced functionality, however, UDDI requires the deployment and -maintenance of a certain amount of infrastructure, thus increasing the cost -of operation. In addition, unless the service descriptions are stored -only within UDDI, there is a cost associated with keeping the different versions -synchronized.</p> - -<p>The WSIL specification relies on a completely distributed model for providing -service-related information. The service descriptions can be stored -at any location, and requests to retrieve the information are generally made -directly to the entities that are offering the services. The WSIL specification -does not stipulate any particular format for the service information. -It relies on other standards, including UDDI, to define the description formats. -The WSIL specification also relies on existing Web technologies and infrastructure -to provide mechanisms for publishing and retrieving its documents.</p> - -<p>WSIL provides the ability to disseminate service-related information through -existing protocols directly from the point at which the service is being offered. -This enables focused discovery to be performed on a single target; however, -because of its decentralized and distributed model, WSIL is not a good mechanism -for executing focused discovery if the communication partner is unknown.</p> - -<p>The UDDI and WSIL specifications should be viewed as complementary technologies -to be used either together or separately depending on the situation. -For example, a UDDI repository could be populated based on the results found -when performing a search for WSIL documents. Likewise, a UDDI repository -may itself be discovered when a requester retrieves a WSIL document that references -an entry in the repository. In environments where the advanced functionality -afforded by UDDI is not required and where constraints do not allow for its -deployment, the WSIL mechanism may provide all of the capabilities that are -needed. In situations where data needs to be centrally managed, a UDDI -solution alone may provide the best fit. The UDDI and WSIL specifications -should not be viewed as mutually exclusive.</p> - -<div class="note"><span class="notetitle">Note: </span>Both UDDI and WSIL contain only references to WSDL - they do not contain -the WSDL documents themselves.</div> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> -<div><a href="cwsil.html" title="Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.">Web Services Inspection Language (WSIL)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing -Web services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita deleted file mode 100644 index dfcefe176..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita +++ /dev/null @@ -1,44 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cwsinwsa" xml:lang="en-us"> -<title>Tools for Web services development</title> -<conbody> -<p>Tools are provided to assist with the following aspects of Web services -development:</p> -<ul> -<li> <uicontrol>Discover</uicontrol>. Browse the UDDI Business Registries -or WSIL documents to locate existing Web services for integration.</li> -<li> <uicontrol>Create or Transform</uicontrol>. Create bottom-up Web services -from existing artifacts, such as <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> beans and enterprise beans. Create -top-down Web services from WSDL discovered from others or created using the -WSDL Editor.</li> -<li> <uicontrol>Build</uicontrol>. Wrap existing artifacts as SOAP accessible -services and describe them in WSDL. The Web services wizards assist you in -generating a <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" -trademark="Java">Java</tm> client proxy to Web services described in WSDL -and in generating <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" -trademark="Java">Java</tm> bean skeletons from WSDL.</li> -<li> <uicontrol>Deploy</uicontrol>. Deploy Web services into a variety of -test environments.</li> -<li> <uicontrol>Test</uicontrol>. Test Web services running locally or remotely -in order to get instant feedback.</li> -<li> <uicontrol>Develop</uicontrol>. Generate sample applications to assist -you in creating your own Web service client application.</li> -<li> <uicontrol>Publish</uicontrol>. Publish Web services to a UDDI v2 or -v3 Business Registry, advertising your Web services so that other businesses -and clie<?Pub Caret?>nts can access them.</li> -</ul> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> -<?Pub *0000002161?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html deleted file mode 100644 index 4e1322585..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html +++ /dev/null @@ -1,83 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Tools for Web services development" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwsinwsa" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Tools for Web services development</title> -</head> -<body id="cwsinwsa"><a name="cwsinwsa"><!-- --></a> - - -<h1 class="topictitle1">Tools for Web services development</h1> - -<div> -<p>Tools are provided to assist with the following aspects of Web services -development:</p> - -<ul> -<li> <span class="uicontrol">Discover</span>. Browse the UDDI Business Registries -or WSIL documents to locate existing Web services for integration.</li> - -<li> <span class="uicontrol">Create or Transform</span>. Create bottom-up Web services -from existing artifacts, such as Java™ beans and enterprise beans. Create -top-down Web services from WSDL discovered from others or created using the -WSDL Editor.</li> - -<li> <span class="uicontrol">Build</span>. Wrap existing artifacts as SOAP accessible -services and describe them in WSDL. The Web services wizards assist you in -generating a Java client proxy to Web services described in WSDL -and in generating Java bean skeletons from WSDL.</li> - -<li> <span class="uicontrol">Deploy</span>. Deploy Web services into a variety of -test environments.</li> - -<li> <span class="uicontrol">Test</span>. Test Web services running locally or remotely -in order to get instant feedback.</li> - -<li> <span class="uicontrol">Develop</span>. Generate sample applications to assist -you in creating your own Web service client application.</li> - -<li> <span class="uicontrol">Publish</span>. Publish Web services to a UDDI v2 or -v3 Business Registry, advertising your Web services so that other businesses -and clients can access them.</li> - -</ul> - -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html">Creating Web services with the Apache Axis run-time environment</a></strong><br /> -</li> -</ul> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita deleted file mode 100644 index 578dadf07..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita +++ /dev/null @@ -1,36 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="cwsiover" xml:lang="en-us"><?Pub Caret?> -<title>Web services interoperability (WS-I)</title> -<shortdesc>WS-I is an organization designed to promote Web service interoperability -across platforms, operating systems, and programming languages.</shortdesc> -<conbody> -<p>For more information on WS-I, refer to their Web site: <xref format="html" -href="http://www.ws-i.org/" scope="external">http://www.ws-i.org/</xref>. -This site contains resources such as an overview of Web services interoperability, -usage scenarios, and specifications.</p> -<p>WS-I Basic Profile is a outline of requirements to which WSDL and Web service -protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. -The Web services WS-I validation tools currently support WS-I Simple SOAP -Binding Profile 1.0 (WS-I SSBP) which builds on the WS-I Basic Profile, and -the WS-I Attachments Profile 1.0 (WS-I AP). To view the specifications, refer -to the WS-I Web site, and under <uicontrol>Deliverables</uicontrol> select - <uicontrol>Basic Profile</uicontrol>.</p> -<p>Depending on the type of Web service being created, you may or may not -want your Web service to comply with the WS-I profiles. The default level -of compliance is to generate a warning if a non WS-I SSBP complaint Web service -option is selected and to ignore any non WS-I AP compliant selections. You -can set the level of WS-I compliance at the workspace or project level. The -Web services wizards, the <tm tmclass="ibm" tmowner="IBM Corporation" tmtype="reg" -trademark="WebSphere">WebSphere</tm> run-time environments, the WSDL editor, -and other Web services tools provided support and encourage the development -of WS-I compliance services.</p> -</conbody> -<related-links> -<linklist><title>Related Tasks</title> -<link href="../tasks/twsicomply.dita"></link> -</linklist> -</related-links> -</concept> -<?Pub *0000002039?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html deleted file mode 100644 index a39d3a3a4..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html +++ /dev/null @@ -1,71 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web services interoperability (WS-I)" /> -<meta name="abstract" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." /> -<meta name="description" content="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/twsicomply.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/twsicomply.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="cwsiover" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Web services interoperability (WS-I)</title> -</head> -<body id="cwsiover"><a name="cwsiover"><!-- --></a> - - -<h1 class="topictitle1">Web services interoperability (WS-I)</h1> - - -<div><p>WS-I is an organization designed to promote Web service interoperability -across platforms, operating systems, and programming languages.</p> - -<p>For more information on WS-I, refer to their Web site: <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a>. -This site contains resources such as an overview of Web services interoperability, -usage scenarios, and specifications.</p> - -<p>WS-I Basic Profile is a outline of requirements to which WSDL and Web service -protocol (SOAP/HTTP) traffic must comply in order to claim WS-I conformance. -The Web services WS-I validation tools currently support WS-I Simple SOAP -Binding Profile 1.0 (WS-I SSBP) which builds on the WS-I Basic Profile, and -the WS-I Attachments Profile 1.0 (WS-I AP). To view the specifications, refer -to the WS-I Web site, and under <span class="uicontrol">Deliverables</span> select - <span class="uicontrol">Basic Profile</span>.</p> - -<p>Depending on the type of Web service being created, you may or may not -want your Web service to comply with the WS-I profiles. The default level -of compliance is to generate a warning if a non WS-I SSBP complaint Web service -option is selected and to ignore any non WS-I AP compliant selections. You -can set the level of WS-I compliance at the workspace or project level. The -Web services wizards, the WebSphere<sup>®</sup> run-time environments, the WSDL editor, -and other Web services tools provided support and encourage the development -of WS-I compliance services.</p> - -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../tasks/twsicomply.html">Setting the level of WS-I compliance</a></strong><br /> -The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant.</li> -</ul> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -</div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/twsicomply.html" title="The Web services WS-I validation tools support the level of WS-I compliance outlined in the WS-I Basic Profile 1.1, the WS-I Simple SOAP Binding Profile 1.0 (WS-I SSBP), and the WS-I Attachments Profile 1.0 (WS-I AP). You can choose to make your Web service compliant or non-compliant, depending on your needs. For example, encoded style (RPC/encoded), SOAP over JMS protocols, and secured Web services, are not WS-I compliant.">Setting the level of WS-I compliance</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita deleted file mode 100644 index 0aadf7c96..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita +++ /dev/null @@ -1,217 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="webservicesstandards" xml:lang="en-us"> -<title>Web services standards</title> -<shortdesc>One of the key attributes of Internet standards is that they focus -on protocols and not on implementations. The Internet is composed of heterogeneous -technologies that successfully interoperate through shared protocols. This -prevents individual vendors from imposing a standard on the Internet. Open -Source software development plays a crucial role in preserving the interoperability -of vendor implementations of standards.</shortdesc> -<conbody> -<p>The following standards play key roles in Web services: Universal Description, -Discovery and Integration (UDDI), Web Services Description Language (WSDL), -Web Services Inspection Language (WSIL), SOAP, and Web Services Interoperability -(WS-I). The relationship between these standards is described in Figure 2.</p> -<p>The UDDI specification defines open, platform-independent standards that -enable businesses to share information in a global business registry, discover -services on the registry, and define how they interact over the Internet. -For more information on UDDI, refer to <xref format="html" href="http://www.uddi.org" -scope="external">www.uddi.org</xref></p> -<p>WSIL is an XML-based open specification that defines a distributed service -discovery method that supplies references to service descriptions at the service -provider's point-of-offering, by specifying how to inspect a Web site for -available Web services. A WSIL document defines the locations on a Web -site where you can look for Web service descriptions. Since WSIL focuses -on distributed service discovery, the WSIL specification complements UDDI -by facilitating the discovery of services that are available on Web sites -that may not be listed yet in a UDDI registry. A separate topic in this -documentation discusses the <xref href="cwsilud.dita">Relationship between -UDDI and WSIL</xref>. For more information on WSIL, refer to <xref -href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" -scope="external"> www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</xref></p> -<p>WSDL is an XML-based open specification that describes the interfaces to -and instances of Web services on the network. It is extensible, so endpoints -can be described regardless of the message formats or network protocols that -are used to communicate. Businesses can make the WSDL documents for their -Web services available though UDDI, WSIL, or by broadcasting the URLs to their -WSDL via email or Web sites. WSDL is described as a separate topic in this -documentation. For more information on WSDL, refer to <xref format="html" -href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p> -<p>SOAP is an XML-based standard for messaging over HTTP and other Internet -protocols. It is a lightweight protocol for the exchange of information in -a decentralized, distributed environment. It is based on XML and consists -of three parts:<ul> -<li>An envelope that defines a framework for describing what is in a message -and how to process it.</li> -<li>A set of encoding rules for expressing instances of application-defined -data types.</li> -<li>A convention for representing remote procedure calls and responses.</li> -</ul>SOAP enables the binding and usage of discovered Web services by defining -a message path for routing messages. SOAP may be used to query UDDI for Web -services. For more information on SOAP, refer to <xref format="html" href="http://www.w3.org/TR/SOAP" -scope="external">www.w3.org/TR/SOAP</xref></p> -<p>Figure 2. Relationships between SOAP, UDDI, WSIL and WSDL.</p> -<p> <image alt="Figure 2 illustrates the relationships between SOAP, UDDI, WSIL, and WSDL." -href="../images/soapudws.gif"></image> </p> -<p>A service provider hosts a Web service and makes it accessible using protocols -such as SOAP/HTTP or SOAP/JMS. The Web service is described by a WSDL document -that is stored on the provider's server or in a special repository. The WSDL -document may be referenced by the UDDI business registry and WSIL documents. -These contain pointers to the Web service's WSDL files.</p> -<p>The WS-I Simple SOAP Binding Profile and WS-I Attachments Profile are outlines -of requirements to which WSDL and Web service protocol (SOAP/HTTP) traffic -must comply in order to claim WS-I conformance. The Web services WS-I validation -tools currently support WS-I Simple SOAP Binding Profile 1.0 and the Attachment -Profile 1.0. To view the specifications, refer to the WS-I Web site, and under - <uicontrol>Resources</uicontrol> select <uicontrol>Documentation</uicontrol>: <xref -href="http://www.ws-i.org" scope="external">http://www.ws-i.org</xref></p> -<p>Several new Web services standards are also supported by <tm tmclass="ibm" -tmowner="IBM Corporation" tmtype="reg" trademark="Rational">Rational</tm> Developer -products. These include:<dl><dlentry> -<dt>JAX-RPC</dt> -<dd>JAX-RPC stands for <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> API for XML-based RPC, also known as -JSR 101. It is a specification that describes <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> Application Programming Interfaces -(APIs) and conventions for building Web services and Web service clients that -use remote procedure calls (RPC) and XML. It standardizes the <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> to -WSDL and WSDL to <tm tmclass="special" tmowner="Sun Microsystems, Inc." tmtype="tm" -trademark="Java">Java</tm> mappings, and provides the core APIs for developing -and deploying Web services and Web service clients on the <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> platform. -For more information refer to the <xref href="http://www.jcp.org/en/jsr/detail?id=101" -scope="external">official specifications</xref>.</dd> -</dlentry><dlentry> -<dt>JSR-109 and JSR-921</dt> -<dd>JSR-109 and JSR-921 (Implementing Enterprise Web Services) define the -programming model and run-time architecture to deploy and look up Web services -in the J2EE environment; more specifically, in the Web, EJB, and Client Application -containers. One of its main goals is to ensure vendors' implementations interoperate. -For more information, refer to the official specifications: <ul> -<li><xref href="http://www.jcp.org/en/jsr/detail?id=109" scope="external" -type="html">JSR-109</xref></li> -<li><xref href="http://www.jcp.org/en/jsr/detail?id=921" scope="external" -type="html">JSR-921</xref></li> -</ul></dd> -</dlentry><dlentry> -<dt>WS-S</dt> -<dd>These tools support the OASIS Web Services Security 1.0 standard. For -more information on the various components of this standard, refer to:<ul> -<li><xref href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" -scope="external" type="html">Web Services Security: SOAP Message Security -V1.0</xref> </li> -<li> <xref href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf" -scope="external" type="html">Web Services Security: Username Token Profile -V1.0</xref></li> -<li> <xref href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf" -scope="external" type="html">Web Services Security: X.509 Token Profile V1.0</xref></li> -</ul></dd> -</dlentry></dl></p> -<p>Web services tooling supports the following specifications:</p> -<table> -<tgroup cols="2"><colspec colname="col1" colwidth="95*"/><colspec colname="col2" -colwidth="104*"/> -<thead> -<row> -<entry colname="col1" valign="top">Technology or specification</entry> -<entry colname="col2" valign="top">Version or level supported</entry> -</row> -</thead> -<tbody> -<row> -<entry nameend="col2" namest="col1"><b>Transports</b></entry> -</row> -<row> -<entry colname="col1">HTTP/HTTPS</entry> -<entry colname="col2">v1.0 and v1.1</entry> -</row> -<row> -<entry colname="col1">JMS</entry> -<entry colname="col2"></entry> -</row> -<row> -<entry nameend="col2" namest="col1"><b>Messaging</b></entry> -</row> -<row> -<entry colname="col1">SOAP specification</entry> -<entry colname="col2">v1.1</entry> -</row> -<row> -<entry colname="col1">SOAP Attachements</entry> -<entry colname="col2"></entry> -</row> -<row> -<entry nameend="col2" namest="col1"><b>Description</b></entry> -</row> -<row> -<entry colname="col1">UDDI</entry> -<entry colname="col2">v2.0</entry> -</row> -<row> -<entry colname="col1">WSDL</entry> -<entry colname="col2">v1.1</entry> -</row> -<row> -<entry colname="col1">WSIL</entry> -<entry colname="col2">v1.0</entry> -</row> -<row> -<entry nameend="col2" namest="col1"><b>Security</b></entry> -</row> -<row> -<entry colname="col1">WS-Security</entry> -<entry colname="col2">OASIS Standard 1.0</entry> -</row> -<row> -<entry nameend="col2" namest="col1"><b>Ineroperability</b></entry> -</row> -<row> -<entry colname="col1">WS-I Basic Profile</entry> -<entry colname="col2">1.1.2</entry> -</row> -<row> -<entry colname="col1">WS-I Simple SOAP Binding Profile</entry> -<entry colname="col2">1.0.3</entry> -</row> -<row> -<entry colname="col1">WS-I Attachments Profile</entry> -<entry colname="col2">1.0</entry> -</row> -<row> -<entry colname="col1"><b>Other Standards</b></entry> -<entry colname="col2"></entry> -</row> -<row> -<entry colname="col1">JAX-RPC</entry> -<entry colname="col2">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</entry> -</row> -<row> -<entry colname="col1">JSR 109</entry> -<entry colname="col2">J2EE 1.3</entry> -</row> -<row> -<entry colname="col1">JSR 921</entry> -<entry colname="col2">J2EE 1.4</entry> -</row> -</tbody> -</tgroup> -</table> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita" scope="local"><linktext>Web services overview</linktext> -</link> -<link href="cwsinwsa.dita" scope="local"><linktext>Tools for Web services -development</linktext></link> -<link href="cwsiover.dita" scope="local"><linktext>Web services interoperability -(WS-I)</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html deleted file mode 100644 index 5feb7bce2..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html +++ /dev/null @@ -1,337 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Web services standards" /> -<meta name="abstract" content="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards." /> -<meta name="description" content="One of the key attributes of Internet standards is that they focus on protocols and not on implementations. The Internet is composed of heterogeneous technologies that successfully interoperate through shared protocols. This prevents individual vendors from imposing a standard on the Internet. Open Source software development plays a crucial role in preserving the interoperability of vendor implementations of standards." /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/csoap.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsil.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cjaxrpc.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cjsr109.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsiover.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="webservicesstandards" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Web services standards</title> -</head> -<body id="webservicesstandards"><a name="webservicesstandards"><!-- --></a> - - -<h1 class="topictitle1">Web services standards</h1> - - -<div><p>One of the key attributes of Internet standards is that they focus -on protocols and not on implementations. The Internet is composed of heterogeneous -technologies that successfully interoperate through shared protocols. This -prevents individual vendors from imposing a standard on the Internet. Open -Source software development plays a crucial role in preserving the interoperability -of vendor implementations of standards.</p> - -<p>The following standards play key roles in Web services: Universal Description, -Discovery and Integration (UDDI), Web Services Description Language (WSDL), -Web Services Inspection Language (WSIL), SOAP, and Web Services Interoperability -(WS-I). The relationship between these standards is described in Figure 2.</p> - -<p>The UDDI specification defines open, platform-independent standards that -enable businesses to share information in a global business registry, discover -services on the registry, and define how they interact over the Internet. -For more information on UDDI, refer to <a href="http://www.uddi.org" target="_blank">www.uddi.org</a></p> - -<p>WSIL is an XML-based open specification that defines a distributed service -discovery method that supplies references to service descriptions at the service -provider's point-of-offering, by specifying how to inspect a Web site for -available Web services. A WSIL document defines the locations on a Web -site where you can look for Web service descriptions. Since WSIL focuses -on distributed service discovery, the WSIL specification complements UDDI -by facilitating the discovery of services that are available on Web sites -that may not be listed yet in a UDDI registry. A separate topic in this -documentation discusses the <a href="cwsilud.html">Relationship between UDDI and WSIL</a>. For more information on WSIL, refer to <a href="http://www-106.ibm.com/developerworks/webservices/library/ws-wsilspec.html" target="_blank">www.ibm.com/developerworks/webservices/library/ws-wsilspec.html</a></p> - -<p>WSDL is an XML-based open specification that describes the interfaces to -and instances of Web services on the network. It is extensible, so endpoints -can be described regardless of the message formats or network protocols that -are used to communicate. Businesses can make the WSDL documents for their -Web services available though UDDI, WSIL, or by broadcasting the URLs to their -WSDL via email or Web sites. WSDL is described as a separate topic in this -documentation. For more information on WSDL, refer to <a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> - -<div class="p">SOAP is an XML-based standard for messaging over HTTP and other Internet -protocols. It is a lightweight protocol for the exchange of information in -a decentralized, distributed environment. It is based on XML and consists -of three parts:<ul> -<li>An envelope that defines a framework for describing what is in a message -and how to process it.</li> - -<li>A set of encoding rules for expressing instances of application-defined -data types.</li> - -<li>A convention for representing remote procedure calls and responses.</li> - -</ul> -SOAP enables the binding and usage of discovered Web services by defining -a message path for routing messages. SOAP may be used to query UDDI for Web -services. For more information on SOAP, refer to <a href="http://www.w3.org/TR/SOAP" target="_blank">www.w3.org/TR/SOAP</a></div> - -<p>Figure 2. Relationships between SOAP, UDDI, WSIL and WSDL.</p> - -<p> <img src="../images/soapudws.gif" alt="Figure 2 illustrates the relationships between SOAP, UDDI, WSIL, and WSDL." /> </p> - -<p>A service provider hosts a Web service and makes it accessible using protocols -such as SOAP/HTTP or SOAP/JMS. The Web service is described by a WSDL document -that is stored on the provider's server or in a special repository. The WSDL -document may be referenced by the UDDI business registry and WSIL documents. -These contain pointers to the Web service's WSDL files.</p> - -<p>The WS-I Simple SOAP Binding Profile and WS-I Attachments Profile are outlines -of requirements to which WSDL and Web service protocol (SOAP/HTTP) traffic -must comply in order to claim WS-I conformance. The Web services WS-I validation -tools currently support WS-I Simple SOAP Binding Profile 1.0 and the Attachment -Profile 1.0. To view the specifications, refer to the WS-I Web site, and under - <span class="uicontrol">Resources</span> select <span class="uicontrol">Documentation</span>: <a href="http://www.ws-i.org" target="_blank">http://www.ws-i.org</a></p> - -<div class="p">Several new Web services standards are also supported by Rational<sup>®</sup> Developer -products. These include:<dl> -<dt class="dlterm">JAX-RPC</dt> - -<dd>JAX-RPC stands for Java™ API for XML-based RPC, also known as -JSR 101. It is a specification that describes Java Application Programming Interfaces -(APIs) and conventions for building Web services and Web service clients that -use remote procedure calls (RPC) and XML. It standardizes the Java to -WSDL and WSDL to Java mappings, and provides the core APIs for developing -and deploying Web services and Web service clients on the Java platform. -For more information refer to the <a href="http://www.jcp.org/en/jsr/detail?id=101" target="_blank">official specifications</a>.</dd> - - -<dt class="dlterm">JSR-109 and JSR-921</dt> - -<dd>JSR-109 and JSR-921 (Implementing Enterprise Web Services) define the -programming model and run-time architecture to deploy and look up Web services -in the J2EE environment; more specifically, in the Web, EJB, and Client Application -containers. One of its main goals is to ensure vendors' implementations interoperate. -For more information, refer to the official specifications: <ul> -<li><a href="http://www.jcp.org/en/jsr/detail?id=109" target="_blank">JSR-109</a></li> - -<li><a href="http://www.jcp.org/en/jsr/detail?id=921" target="_blank">JSR-921</a></li> - -</ul> -</dd> - - -<dt class="dlterm">WS-S</dt> - -<dd>These tools support the OASIS Web Services Security 1.0 standard. For -more information on the various components of this standard, refer to:<ul> -<li><a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0.pdf" target="_blank">Web Services Security: SOAP Message Security V1.0</a> </li> - -<li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0.pdf" target="_blank">Web Services Security: Username Token Profile V1.0</a></li> - -<li> <a href="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0.pdf" target="_blank">Web Services Security: X.509 Token Profile V1.0</a></li> - -</ul> -</dd> - -</dl> -</div> - -<p>Web services tooling supports the following specifications:</p> - - -<div class="tablenoborder"><table summary="" cellspacing="0" cellpadding="4" frame="border" border="1" rules="all"> -<thead align="left"> -<tr> -<th valign="top" width="47.73869346733669%" id="N101A4">Technology or specification</th> - -<th valign="top" width="52.26130653266332%" id="N101AC">Version or level supported</th> - -</tr> - -</thead> - -<tbody> -<tr> -<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Transports</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">HTTP/HTTPS</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.0 and v1.1</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">JMS</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC "> </td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Messaging</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">SOAP specification</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.1</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">SOAP Attachements</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC "> </td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Description</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">UDDI</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">v2.0</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">WSDL</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.1</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">WSIL</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.0</td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Security</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-Security</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">OASIS Standard 1.0</td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101A4 N101AC "><strong>Ineroperability</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-I Basic Profile</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">1.1.2</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-I Simple SOAP Binding Profile</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">1.0.3</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">WS-I Attachments Profile</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">1.0</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 "><strong>Other Standards</strong></td> - -<td valign="top" width="52.26130653266332%" headers="N101AC "> </td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">JAX-RPC</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">JSR 109</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">J2EE 1.3</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101A4 ">JSR 921</td> - -<td valign="top" width="52.26130653266332%" headers="N101AC ">J2EE 1.4</td> - -</tr> - -</tbody> - -</table> -</div> - -</div> - -<div> -<ul class="ullinks"> -<li class="ulchildlink"><strong><a href="../concepts/cwsdl.html">Web Services Description Language (WSDL)</a></strong><br /> -Web Services Description Language (WSDL) is a standard specification for describing networked, XML-based services. It provides a simple way for service providers to describe the basic format of requests to their systems regardless of the underlying run-time implementation.</li> -<li class="ulchildlink"><strong><a href="../concepts/csoap.html">SOAP</a></strong><br /> -SOAP (formerly known as Simple Object Access Protocol) is a lightweight protocol for the exchange of information in a decentralized, distributed environment. A SOAP message is a transmission of information from a sender to a receiver. SOAP messages can be combined to perform request/response patterns.</li> -<li class="ulchildlink"><strong><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html">Universal Description, Discovery, and Integration (UDDI)</a></strong><br /> -</li> -<li class="ulchildlink"><strong><a href="../concepts/cwsil.html">Web Services Inspection Language (WSIL)</a></strong><br /> -Web Services Inspection Language (WSIL) is a service discovery mechanism that is an alternative to UDDI as well as complementary to UDDI. When you discover Web services with UDDI, you go to a centralized registry. WSIL is an alternative approach to Web service discovery. WSIL allows you to go directly to the service provider and ask for the services it provides.</li> -<li class="ulchildlink"><strong><a href="../concepts/cjaxrpc.html">JAX-RPC</a></strong><br /> -JAX-RPC stands for Java API for XML-based RPC, also known as JSR 101. It is a specification that describes Java Application Programming Interfaces (APIs) and conventions for building Web services and Web service clients that use remote procedure calls (RPC) and XML. It standardizes the Java to WSDL and WSDL to Java mappings, and provides the core APIs for developing Web services and Web service clients on the Java platform. Often used in a distributed client/server model, an RPC mechanism enables clients to execute procedures on other systems.</li> -<li class="ulchildlink"><strong><a href="../concepts/cjsr109.html">JSR 109 and JSR 921- Implementing Enterprise Web services</a></strong><br /> -JSR 109 and JSR 921 (Implementing Enterprise Web Services) define the programming model and run-time architecture to deploy and look up Web services in the J2EE environment; more specifically, in the Web, EJB, and Client Application containers. One of its main goals is to ensure vendors' implementations interoperate.</li> -</ul> - -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../concepts/cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services -development</a></div> -<div><a href="cwsiover.html" title="WS-I is an organization designed to promote Web service interoperability across platforms, operating systems, and programming languages.">Web services interoperability -(WS-I)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita deleted file mode 100644 index b15b6ceeb..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita +++ /dev/null @@ -1,32 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE concept PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> -<concept id="creatingtop-downwebservices" xml:lang="en-us"><?Pub Caret?> -<title>Creating top-down Web services</title> -<shortdesc>Web services can be created using two methods: top-down development -and bottom-up development. Top-down Web services development involves creating -a Web service from a WSDL file.</shortdesc> -<conbody> -<p>Although bottom-up Web service development may be faster and easier, especially -if you are new to Web services, the top-down approach is the recommended way -of creating a Web service.</p> -<p>When creating a Web service using a top-down approach, first you design -the implementation of the Web service by creating a WSDL file. You can do -this using the WSDL Editor. You can then use the Web services wizard to create -the Web service and skeleton <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> classes to which you can add the required -code.</p> -</conbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="cws.dita"></link> -<link href="cwsinwsa.dita"></link> -<link href="cwsbtmup.dita" scope="local"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="local"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> -<?Pub *0000001482?> diff --git a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html b/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html deleted file mode 100644 index cf7c7937d..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html +++ /dev/null @@ -1,65 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> -<html lang="en-us" xml:lang="en-us"> -<head> -<meta content="text/html; charset=utf-8" http-equiv="Content-Type" /> -<meta name="copyright" content="(C) Copyright 2005" /> -<meta name="DC.rights.owner" content="(C) Copyright 2005" /> -<meta content="public" name="security" /> -<meta content="index,follow" name="Robots" /> -<meta http-equiv="PICS-Label" content='(PICS-1.1 "http://www.icra.org/ratingsv02.html" l gen true r (cz 1 lz 1 nz 1 oz 1 vz 1) "http://www.rsac.org/ratingsv01.html" l gen true r (n 0 s 0 v 0 l 0) "http://www.classify.org/safesurf/" l gen true r (SS~~000 1))' /> -<meta content="concept" name="DC.Type" /> -<meta name="DC.Title" content="Creating top-down Web services" /> -<meta name="abstract" content="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file." /> -<meta name="description" content="Web services can be created using two methods: top-down development and bottom-up development. Top-down Web services development involves creating a Web service from a WSDL file." /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta scheme="URI" name="DC.Relation" content="cws.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="cwsbtmup.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="creatingtop-downwebservices" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/commonltr.css" type="text/css" rel="stylesheet" /> -<title>Creating top-down Web services</title> -</head> -<body id="creatingtop-downwebservices"><a name="creatingtop-downwebservices"><!-- --></a> - - -<h1 class="topictitle1">Creating top-down Web services</h1> - - -<div><p>Web services can be created using two methods: top-down development -and bottom-up development. Top-down Web services development involves creating -a Web service from a WSDL file.</p> - -<p>Although bottom-up Web service development may be faster and easier, especially -if you are new to Web services, the top-down approach is the recommended way -of creating a Web service.</p> - -<p>When creating a Web service using a top-down approach, first you design -the implementation of the Web service by creating a WSDL file. You can do -this using the WSDL Editor. You can then use the Web services wizard to create -the Web service and skeleton Java™ classes to which you can add the required -code.</p> - -</div> - -<div> -<div class="familylinks"> -<div class="parentlink"><strong>Parent topic:</strong> <a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB).">Developing Web services</a></div> -</div> - -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="cws.html" title="A Web service is a set of related application functions that can be programmatically invoked over the Internet. Businesses can dynamically mix and match Web services to perform complex transactions with minimal programming. Web services allow buyers and sellers all over the world to discover each other, connect dynamically, and execute transactions in real time with minimal human interaction.">Web services overview</a></div> -<div><a href="cwsinwsa.html" title="">Tools for Web services development</a></div> -<div><a href="cwsbtmup.html" title="Web services can be created using two methods: top-down development and bottom-up development. Bottom-up Web services development involves creating a Web service from a Java bean or enterprise bean.">Creating bottom-up Web services</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html" title="Use Web services tools to discover, create, and publish Web services that are created from Java beans, enterprise beans, and WSDL files. You can create of Web services using a top-down approach (which starts with a WSDL file) or a bottom-up approach (which starts with a Java bean or EJB)."> Developing Web -services</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file |