diff options
Diffstat (limited to 'docs/org.eclipse.jst.ws.doc.user')
54 files changed, 0 insertions, 3818 deletions
diff --git a/docs/org.eclipse.jst.ws.doc.user/.cvsignore b/docs/org.eclipse.jst.ws.doc.user/.cvsignore deleted file mode 100644 index c6a7b236c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/.cvsignore +++ /dev/null @@ -1,5 +0,0 @@ -org.eclipse.jst.ws.doc.user_1.0.0.jar -bak -temp -build.xml -out
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/.project b/docs/org.eclipse.jst.ws.doc.user/.project deleted file mode 100644 index b0cfef708..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/.project +++ /dev/null @@ -1,22 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<projectDescription> - <name>org.eclipse.jst.ws.doc.user</name> - <comment></comment> - <projects> - </projects> - <buildSpec> - <buildCommand> - <name>org.eclipse.pde.ManifestBuilder</name> - <arguments> - </arguments> - </buildCommand> - <buildCommand> - <name>org.eclipse.pde.SchemaBuilder</name> - <arguments> - </arguments> - </buildCommand> - </buildSpec> - <natures> - <nature>org.eclipse.pde.PluginNature</nature> - </natures> -</projectDescription> diff --git a/docs/org.eclipse.jst.ws.doc.user/DocBuild.xml b/docs/org.eclipse.jst.ws.doc.user/DocBuild.xml deleted file mode 100644 index 123957c22..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/DocBuild.xml +++ /dev/null @@ -1,59 +0,0 @@ -<?xml version="1.0" encoding="UTF-8" ?> -<!-- - - This script build the Help plug-in by transforming the DITA source files into HTML. - - To use this script, you must install DITA-OT on your machine in the directory - defined by the dita.ot.dir property. - - Run the default target after you edit the DITA source files to regenerate the HTML. - - To customize this script for other Help plug-ins, modify the value of the args.input property - to be the DITA map file for the plug-in. - - NOTE: This script assumes that links to sibling Help plug-ins have scope="peer", otherwise the - output directory structure will be shifted incorrectly. - - NOTE: This script assumes that you hand code your plugin.xml file in myplugin.xml. This file - will be copied over the generated plugin.xml which is currently not being generated correctly - by DITA-OT. - - ChangeLog: - 2006-04-05 Arthur Ryman <ryman@ca.ibm.com> - - Created. - ---> -<project name="eclipsehelp" default="all"> - - <property name="dita.ot.dir" location="C:/DITA-OT1.2.2" /> - - <path id="dost.class.path"> - <pathelement location="${dita.ot.dir}${file.separator}lib${file.separator}dost.jar" /> - </path> - - <taskdef name="integrate" classname="org.dita.dost.platform.IntegratorTask"> - <classpath refid="dost.class.path" /> - </taskdef> - <target name="all" depends="integrate, eclipsehelp"> - </target> - <target name="integrate"> - <integrate ditadir="${dita.ot.dir}" /> - </target> - - <!-- revise below here --> - <target name="eclipsehelp"> - <ant antfile="${dita.ot.dir}${file.separator}conductor.xml" target="init" dir="${dita.ot.dir}"> - <property name="args.copycss" value="no" /> - <property name="args.csspath" value="org.eclipse.wst.doc.user" /> - <property name="args.eclipse.provider" value="Eclipse.org" /> - <property name="args.eclipse.version" value="1.5.0" /> - <property name="args.input" location="webservice_toc.ditamap" /> - <property name="clean.temp" value="true" /> - <property name="dita.extname" value=".dita" /> - <property name="dita.temp.dir" location="temp" /> - <property name="output.dir" location=".." /> - <property name="transtype" value="eclipsehelp" /> - </ant> - <copy file="myplugin.xml" tofile="plugin.xml" overwrite="yes" /> - </target> -</project> diff --git a/docs/org.eclipse.jst.ws.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.jst.ws.doc.user/META-INF/MANIFEST.MF deleted file mode 100644 index ad15e38c5..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/META-INF/MANIFEST.MF +++ /dev/null @@ -1,7 +0,0 @@ -Manifest-Version: 1.0 -Bundle-ManifestVersion: 2 -Bundle-Name: %pluginName -Bundle-SymbolicName: org.eclipse.jst.ws.doc.user; singleton:=true -Bundle-Version: 1.0.300.qualifier -Bundle-Vendor: %pluginProvider -Bundle-Localization: plugin diff --git a/docs/org.eclipse.jst.ws.doc.user/about.html b/docs/org.eclipse.jst.ws.doc.user/about.html deleted file mode 100644 index 73db36ed5..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/about.html +++ /dev/null @@ -1,34 +0,0 @@ -<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0//EN"> -<HTML> - -<head> -<title>About</title> -<meta http-equiv=Content-Type content="text/html; charset=ISO-8859-1"> -</head> - -<BODY lang="EN-US"> - -<H3>About This Content</H3> - -<P>June 06, 2007</P> - -<H3>License</H3> - -<P>The Eclipse Foundation makes available all content in this plug-in -("Content"). Unless otherwise indicated below, the Content is provided to you -under the terms and conditions of the Eclipse Public License Version 1.0 -("EPL"). A copy of the EPL is available at -<A href="http://www.eclipse.org/org/documents/epl-v10.php">http://www.eclipse.org/org/documents/epl-v10.php</A>. -For purposes of the EPL, "Program" will mean the Content.</P> - -<P>If you did not receive this Content directly from the Eclipse Foundation, the -Content is being redistributed by another party ("Redistributor") and different -terms and conditions may apply to your use of any object code in the Content. -Check the Redistributor’s license that was provided with the Content. If no such -license exists, contact the Redistributor. Unless otherwise indicated below, the -terms and conditions of the EPL still apply to any source code in the Content -and such source code may be obtained at -<A href="http://www.eclipse.org/">http://www.eclipse.org/</A>.</P> - -</BODY> -</HTML> diff --git a/docs/org.eclipse.jst.ws.doc.user/build.properties b/docs/org.eclipse.jst.ws.doc.user/build.properties deleted file mode 100644 index 0395e5722..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/build.properties +++ /dev/null @@ -1,19 +0,0 @@ -bin.includes = plugin.properties,\ - plugin.xml,\ - webservice_toc.xml,\ - org.eclipse.jst.ws.doc.userindex.xml,\ - about.html,\ - images/,\ - concepts/*.htm*,\ - tasks/*.htm*,\ - ref/*.htm*,\ - index/,\ - META-INF/ -src.includes = build.properties,\ - *.maplist,\ - *.ditamap,\ - concepts/*.dita,\ - tasks/*.dita,\ - ref/*.dita -bin.excludes = DocBuild.xml,\ - myPlugin*.xml 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 d3b5b27b8..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.dita +++ /dev/null @@ -1,66 +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"> -<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> -<prolog><metadata> -<keywords><indexterm>JAX-RPC<indexterm>Web services</indexterm></indexterm> -<indexterm>Web services<indexterm>JAX-RPC</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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> 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 f1202d42b..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html +++ /dev/null @@ -1,84 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="JAX-RPC, Web services" name="DC.subject" /> -<meta content="JAX-RPC, Web services" name="keywords" /> -<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/common.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="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 189a30781..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.dita +++ /dev/null @@ -1,41 +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> -<prolog><metadata> -<keywords><indexterm>JSR 109 Java specification</indexterm> -<indexterm>JSR 921 Java specification</indexterm> -<indexterm>Web services<indexterm>Java specification requests</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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 0a4dd2e71..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html +++ /dev/null @@ -1,64 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="JSR 109 Java specification, JSR 921 Java specification, Web services, Java specification requests" name="DC.subject" /> -<meta content="JSR 109 Java specification, JSR 921 Java specification, Web services, Java specification requests" name="keywords" /> -<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/common.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="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 4237c2756..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.dita +++ /dev/null @@ -1,108 +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> -<prolog><metadata> -<keywords><indexterm>SOAP<indexterm>overview</indexterm></indexterm> -<indexterm>Web services<indexterm>SOAP</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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.3, 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 2eaf618f3..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/csoap.html +++ /dev/null @@ -1,154 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="SOAP, overview, Web services" name="DC.subject" /> -<meta content="SOAP, overview, Web services" name="keywords" /> -<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/common.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.3, 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="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 b0e628674..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.dita +++ /dev/null @@ -1,93 +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> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>overview</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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.ibm.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 80d7ce1ae..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cws.html +++ /dev/null @@ -1,137 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="Web services, overview" name="DC.subject" /> -<meta content="Web services, overview" name="keywords" /> -<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/common.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.ibm.com/developerworks/webservices</a></p> -</div> - -</div> - -<div> -<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 b18f7fbf5..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.dita +++ /dev/null @@ -1,38 +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"> -<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> -<prolog><metadata> -<keywords><indexterm>bottom-up Web services<indexterm>overview</indexterm></indexterm> -<indexterm>Web services<indexterm>bottom-up</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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> 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 c2bfaf49a..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html +++ /dev/null @@ -1,63 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="bottom-up Web services, overview, Web services, bottom-up" name="DC.subject" /> -<meta content="bottom-up Web services, overview, Web services, bottom-up" name="keywords" /> -<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/common.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="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 cc89e9f5c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.dita +++ /dev/null @@ -1,73 +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="cwsdl" xml:lang="en-us"> -<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> -<prolog><metadata> -<keywords><indexterm>WSDL<indexterm>overview</indexterm></indexterm><indexterm>Web -services<indexterm>WSDL</indexterm></indexterm></keywords> -</metadata></prolog> -<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> 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 c5f8199de..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html +++ /dev/null @@ -1,102 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="WSDL, overview, Web services" name="DC.subject" /> -<meta content="WSDL, overview, Web services" name="keywords" /> -<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/common.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> -<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 2b10f2352..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.dita +++ /dev/null @@ -1,84 +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> -<prolog><metadata> -<keywords><indexterm>WSIL<indexterm>overview</indexterm></indexterm><indexterm>Web -services<indexterm>WSIL</indexterm></indexterm></keywords> -</metadata></prolog> -<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 4720f018c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsil.html +++ /dev/null @@ -1,120 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="WSIL, overview, Web services" name="DC.subject" /> -<meta content="WSIL, overview, Web services" name="keywords" /> -<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/common.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> -<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 6a58a0b35..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.dita +++ /dev/null @@ -1,72 +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> -<prolog><metadata> -<keywords><indexterm>UDDI<indexterm>relationship with WSIL</indexterm></indexterm> -<indexterm>WSIL<indexterm>relationship with UDDI</indexterm></indexterm></keywords> -</metadata></prolog> -<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"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</concept> 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 533c44d57..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html +++ /dev/null @@ -1,104 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="UDDI, relationship with WSIL, WSIL, relationship with UDDI" name="DC.subject" /> -<meta content="UDDI, relationship with WSIL, WSIL, relationship with UDDI" name="keywords" /> -<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/common.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="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 5cd0a1887..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.dita +++ /dev/null @@ -1,48 +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> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>tools overview</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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 clients 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> 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 ec0887d88..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html +++ /dev/null @@ -1,75 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="Web services, tools overview" name="DC.subject" /> -<meta content="Web services, tools overview" name="keywords" /> -<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/common.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> -<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 a0755248f..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.dita +++ /dev/null @@ -1,41 +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"> -<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> -<prolog><metadata> -<keywords><indexterm>Web services interoperability<indexterm>traffic compliance</indexterm></indexterm> -<indexterm>interoperability<indexterm>Web service traffic compliance</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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> 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 98ea14bd4..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html +++ /dev/null @@ -1,63 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="Web services interoperability, traffic compliance, interoperability, Web service traffic compliance" name="DC.subject" /> -<meta content="Web services interoperability, traffic compliance, interoperability, Web service traffic compliance" name="keywords" /> -<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/common.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> -<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 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 f49a95fde..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.dita +++ /dev/null @@ -1,222 +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> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>standards</indexterm></indexterm> -</keywords> -</metadata></prolog> -<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 1.1 (SOAP 1.2 is not supported by the -Web services tools), 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 this development -environment. 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 2ac503667..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html +++ /dev/null @@ -1,315 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="Web services, standards" name="DC.subject" /> -<meta content="Web services, standards" name="keywords" /> -<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/common.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 1.1 (SOAP 1.2 is not supported by the -Web services tools), 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 this development -environment. 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="N101B4">Technology or specification</th> - -<th valign="top" width="52.26130653266332%" id="N101BC">Version or level supported</th> - -</tr> - -</thead> - -<tbody> -<tr> -<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Transports</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">HTTP/HTTPS</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.0 and v1.1</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">JMS</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC "> </td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Messaging</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">SOAP specification</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.1</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">SOAP Attachements</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC "> </td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Description</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">UDDI</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">v2.0</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">WSDL</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.1</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">WSIL</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.0</td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Security</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-Security</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">OASIS Standard 1.0</td> - -</tr> - -<tr> -<td colspan="2" valign="top" headers="N101B4 N101BC "><strong>Ineroperability</strong></td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-I Basic Profile</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">1.1.2</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-I Simple SOAP Binding Profile</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">1.0.3</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">WS-I Attachments Profile</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">1.0</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 "><strong>Other Standards</strong></td> - -<td valign="top" width="52.26130653266332%" headers="N101BC "> </td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">JAX-RPC</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">v1.0 for J2EE 1.3, v1.1 for J2EE 1.4</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">JSR 109</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">J2EE 1.3</td> - -</tr> - -<tr> -<td valign="top" width="47.73869346733669%" headers="N101B4 ">JSR 921</td> - -<td valign="top" width="52.26130653266332%" headers="N101BC ">J2EE 1.4</td> - -</tr> - -</tbody> - -</table> -</div> - -</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 cc1676d6f..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.dita +++ /dev/null @@ -1,39 +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"> -<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> -<prolog><metadata> -<keywords><indexterm>top-down Web services<indexterm>creating</indexterm></indexterm> -<indexterm>Web services<indexterm>top-down</indexterm></indexterm> -</keywords> -</metadata></prolog> -<conbody> -<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> -<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. By creating the WSDL file first you will ultimately -have more control over the Web service, and can eliminate interoperability -issues that may arise when creating a Web service using the bottom-up method.</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> 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 1124a8ba6..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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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 content="top-down Web services, creating, Web services, top-down" name="DC.subject" /> -<meta content="top-down Web services, creating, Web services, top-down" name="keywords" /> -<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/common.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>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> - -<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. By creating the WSDL file first you will ultimately -have more control over the Web service, and can eliminate interoperability -issues that may arise when creating a Web service using the bottom-up method.</p> - -</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 diff --git a/docs/org.eclipse.jst.ws.doc.user/images/roles.gif b/docs/org.eclipse.jst.ws.doc.user/images/roles.gif Binary files differdeleted file mode 100644 index 05e99874a..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/images/roles.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif b/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif Binary files differdeleted file mode 100644 index efb42f500..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/images/soapudws.gif +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.doc.user/index/_w.cfs b/docs/org.eclipse.jst.ws.doc.user/index/_w.cfs Binary files differdeleted file mode 100644 index e8eb6fb18..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/index/_w.cfs +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.doc.user/index/deletable b/docs/org.eclipse.jst.ws.doc.user/index/deletable Binary files differdeleted file mode 100644 index e423242b3..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/index/deletable +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.doc.user/index/indexed_contributions b/docs/org.eclipse.jst.ws.doc.user/index/indexed_contributions deleted file mode 100644 index 8a87d8d1c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/index/indexed_contributions +++ /dev/null @@ -1,3 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:13:37 EDT 2007
-org.eclipse.jst.ws.doc.user=org.eclipse.jst.ws.doc.user\n1.0.300.qualifier
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/indexed_dependencies b/docs/org.eclipse.jst.ws.doc.user/index/indexed_dependencies deleted file mode 100644 index 02fe41d6c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/index/indexed_dependencies +++ /dev/null @@ -1,4 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:13:37 EDT 2007
-lucene=1.4.103.v20060601
-analyzer=org.eclipse.help.base\#3.2.0.v20060601?locale\=en
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/indexed_docs b/docs/org.eclipse.jst.ws.doc.user/index/indexed_docs deleted file mode 100644 index 229f8fd70..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/index/indexed_docs +++ /dev/null @@ -1,31 +0,0 @@ -#This is a generated file; do not edit.
-#Wed May 09 14:13:37 EDT 2007
-/org.eclipse.jst.ws.doc.user/concepts/cwsbtmup.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwstopdown.html=0
-/org.eclipse.jst.ws.doc.user/ref/rwspref.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html=0
-/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwsdl.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwsinwsa.html=0
-/org.eclipse.jst.ws.doc.user/ref/rwsdl.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html=0
-/org.eclipse.jst.ws.doc.user/concepts/csoap.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html=0
-/org.eclipse.jst.ws.doc.user/tasks/toverws.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwsstandards.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cws.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cjaxrpc.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwsiover.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwsil.html=0
-/org.eclipse.jst.ws.doc.user/../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cwsilud.html=0
-/org.eclipse.jst.ws.doc.user/concepts/cjsr109.html=0
diff --git a/docs/org.eclipse.jst.ws.doc.user/index/segments b/docs/org.eclipse.jst.ws.doc.user/index/segments Binary files differdeleted file mode 100644 index 19b5d0c42..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/index/segments +++ /dev/null diff --git a/docs/org.eclipse.jst.ws.doc.user/myplugin.xml b/docs/org.eclipse.jst.ws.doc.user/myplugin.xml deleted file mode 100644 index ef8b20b32..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/myplugin.xml +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="webservice_toc.xml" /> - <index path="index/"/> - </extension> - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.jst.ws.doc.userindex.xml"/> - </extension> -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.user.maplist b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.user.maplist deleted file mode 100644 index b266991a9..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.user.maplist +++ /dev/null @@ -1,8 +0,0 @@ -<maplist version="3.6.2"> - <nav> - <map file="webservice_toc.ditamap"/> - </nav> - <link> - <map file="webservice_toc.ditamap"/> - </link> -</maplist> diff --git a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.html b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.html deleted file mode 100644 index cf9505e7c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.html +++ /dev/null @@ -1,164 +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 http-equiv="Content-Type" content="text/html; charset=utf-8" /> -<meta name="copyright" content="(C) Copyright IBM Corporation 2007" /> -<meta name="security" content="public" /> -<meta name="Robots" content="index,follow" /> -<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 name="DC.Format" content="XHTML" /> -<!-- All rights reserved. Licensed Materials Property of IBM --> -<!-- US Government Users Restricted Rights --> -<!-- Use, duplication or disclosure restricted by --> -<!-- GSA ADP Schedule Contract with IBM Corp. --> -<link rel="stylesheet" type="text/css" href="ibmdita.css" /> -<title>Index</title> -</head> -<body> -<h1>Index</h1> -<a name="IDX0_42" href="#IDX1_42">B</a> -<a name="IDX0_49" href="#IDX1_49">I</a> -<a name="IDX0_4A" href="#IDX1_4A">J</a> -<a name="IDX0_50" href="#IDX1_50">P</a> -<a name="IDX0_53" href="#IDX1_53">S</a> -<a name="IDX0_54" href="#IDX1_54">T</a> -<a name="IDX0_55" href="#IDX1_55">U</a> -<a name="IDX0_57" href="#IDX1_57">W</a> -<hr></hr> -<strong><a name="IDX1_42" href="#IDX0_42">B</a></strong> -<ul class="indexlist"> -<li>bottom-up Web services -<ul class="indexlist"> -<li><a href="concepts/cwsbtmup.html#creatingbottom-upwebservices">overview</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_49" href="#IDX0_49">I</a></strong> -<ul class="indexlist"> -<li>interoperability -<ul class="indexlist"> -<li><a href="concepts/cwsiover.html#cwsiover">Web service traffic compliance</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_4A" href="#IDX0_4A">J</a></strong> -<ul class="indexlist"> -<li>JAX-RPC -<ul class="indexlist"> -<li><a href="concepts/cjaxrpc.html#cjaxrpc">Web services</a> -</li> -</ul> -</li> -<li><a href="concepts/cjsr109.html#cjsr109">JSR 109 Java specification</a> -</li> -<li><a href="concepts/cjsr109.html#cjsr109">JSR 921 Java specification</a> -</li> -</ul> -<strong><a name="IDX1_50" href="#IDX0_50">P</a></strong> -<ul class="indexlist"> -<li>preferences -<ul class="indexlist"> -<li><a href="ref/rwspref.html#rwspref">Web services</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_53" href="#IDX0_53">S</a></strong> -<ul class="indexlist"> -<li>SOAP -<ul class="indexlist"> -<li><a href="concepts/csoap.html#csoap">overview</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_54" href="#IDX0_54">T</a></strong> -<ul class="indexlist"> -<li>top-down Web services -<ul class="indexlist"> -<li><a href="concepts/cwstopdown.html#creatingtop-downwebservices">creating</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_55" href="#IDX0_55">U</a></strong> -<ul class="indexlist"> -<li>UDDI -<ul class="indexlist"> -<li><a href="concepts/cwsilud.html#cwsilud">relationship with WSIL</a> -</li> -</ul> -</li> -</ul> -<strong><a name="IDX1_57" href="#IDX0_57">W</a></strong> -<ul class="indexlist"> -<li>Web services -<ul class="indexlist"> -<li><a href="concepts/cwsbtmup.html#creatingbottom-upwebservices">bottom-up</a> -</li> -<li>creating -<ul class="indexlist"> -<li><a href="tasks/toverws.html#toverws">overview</a> -</li> -</ul> -</li> -<li><a href="tasks/twsicomply.html#twsicomply">interoperability compliance</a> -</li> -<li><a href="concepts/cjsr109.html#cjsr109">Java specification requests</a> -</li> -<li><a href="concepts/cjaxrpc.html#cjaxrpc">JAX-RPC</a> -</li> -<li><a href="concepts/cws.html#cws">overview</a> -</li> -<li><a href="ref/rwspref.html#rwspref">preferences</a> -</li> -<li><a href="concepts/csoap.html#csoap">SOAP</a> -</li> -<li><a href="concepts/cwsstandards.html#webservicesstandards">standards</a> -</li> -<li><a href="concepts/cwsinwsa.html#cwsinwsa">tools overview</a> -</li> -<li><a href="concepts/cwstopdown.html#creatingtop-downwebservices">top-down</a> -</li> -<li><a href="concepts/cwsdl.html#cwsdl">WSDL</a> -</li> -<li><a href="ref/rwsdl.html#rwsdl">WSDL reference</a> -</li> -<li><a href="concepts/cwsil.html#cwsil">WSIL</a> -</li> -</ul> -</li> -<li>Web services interoperability -<ul class="indexlist"> -<li><a href="concepts/cwsiover.html#cwsiover">traffic compliance</a> -</li> -</ul> -</li> -<li>WSDL -<ul class="indexlist"> -<li><a href="concepts/cwsdl.html#cwsdl">overview</a> -</li> -<li><a href="ref/rwsdl.html#rwsdl">reference</a> -</li> -</ul> -</li> -<li>WSI -<ul class="indexlist"> -<li><a href="tasks/twsicomply.html#twsicomply">setting compliance</a> -</li> -</ul> -</li> -<li>WSIL -<ul class="indexlist"> -<li><a href="concepts/cwsil.html#cwsil">overview</a> -</li> -<li><a href="concepts/cwsilud.html#cwsilud">relationship with UDDI</a> -</li> -</ul> -</li> -</ul> -</body></html> diff --git a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.xml b/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.xml deleted file mode 100644 index 9d6673aad..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/org.eclipse.jst.ws.doc.userindex.xml +++ /dev/null @@ -1,116 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<index> - <entry keyword="Web services"> - <entry keyword="overview"> - <topic href="concepts/cws.html#cws" title="Web services overview"/> - </entry> - <entry keyword="standards"> - <topic href="concepts/cwsstandards.html#webservicesstandards" title="Web services standards"/> - </entry> - <entry keyword="WSDL"> - <topic href="concepts/cwsdl.html#cwsdl" title="Web Services Description Language (WSDL)"/> - </entry> - <entry keyword="WSDL reference"> - <topic href="ref/rwsdl.html#rwsdl" title="Web Services Description Language (WSDL) reference"/> - </entry> - <entry keyword="SOAP"> - <topic href="concepts/csoap.html#csoap" title="SOAP"/> - </entry> - <entry keyword="WSIL"> - <topic href="concepts/cwsil.html#cwsil" title="Web Services Inspection Language (WSIL)"/> - </entry> - <entry keyword="JAX-RPC"> - <topic href="concepts/cjaxrpc.html#cjaxrpc" title="JAX-RPC"/> - </entry> - <entry keyword="Java specification requests"> - <topic href="concepts/cjsr109.html#cjsr109" title="JSR 109 and JSR 921- Implementing Enterprise Web services"/> - </entry> - <entry keyword="tools overview"> - <topic href="concepts/cwsinwsa.html#cwsinwsa" title="Tools for Web services development"/> - </entry> - <entry keyword="preferences"> - <topic href="ref/rwspref.html#rwspref" title="Web services preferences"/> - </entry> - <entry keyword="interoperability compliance"> - <topic href="tasks/twsicomply.html#twsicomply" title="Setting the level of WS-I compliance"/> - </entry> - <entry keyword="creating"> - <entry keyword="overview"> - <topic href="tasks/toverws.html#toverws" title="Developing Web services"/> - </entry> - </entry> - <entry keyword="top-down"> - <topic href="concepts/cwstopdown.html#creatingtop-downwebservices" title="Creating top-down Web services"/> - </entry> - <entry keyword="bottom-up"> - <topic href="concepts/cwsbtmup.html#creatingbottom-upwebservices" title="Creating bottom-up Web services"/> - </entry> - </entry> - <entry keyword="WSDL"> - <entry keyword="overview"> - <topic href="concepts/cwsdl.html#cwsdl" title="Web Services Description Language (WSDL)"/> - </entry> - <entry keyword="reference"> - <topic href="ref/rwsdl.html#rwsdl" title="Web Services Description Language (WSDL) reference"/> - </entry> - </entry> - <entry keyword="SOAP"> - <entry keyword="overview"> - <topic href="concepts/csoap.html#csoap" title="SOAP"/> - </entry> - </entry> - <entry keyword="WSIL"> - <entry keyword="overview"> - <topic href="concepts/cwsil.html#cwsil" title="Web Services Inspection Language (WSIL)"/> - </entry> - <entry keyword="relationship with UDDI"> - <topic href="concepts/cwsilud.html#cwsilud" title="Relationship between UDDI and WSIL"/> - </entry> - </entry> - <entry keyword="UDDI"> - <entry keyword="relationship with WSIL"> - <topic href="concepts/cwsilud.html#cwsilud" title="Relationship between UDDI and WSIL"/> - </entry> - </entry> - <entry keyword="JAX-RPC"> - <entry keyword="Web services"> - <topic href="concepts/cjaxrpc.html#cjaxrpc" title="JAX-RPC"/> - </entry> - </entry> - <entry keyword="JSR 109 Java specification"> - <topic href="concepts/cjsr109.html#cjsr109" title="JSR 109 and JSR 921- Implementing Enterprise Web services"/> - </entry> - <entry keyword="JSR 921 Java specification"> - <topic href="concepts/cjsr109.html#cjsr109" title="JSR 109 and JSR 921- Implementing Enterprise Web services"/> - </entry> - <entry keyword="preferences"> - <entry keyword="Web services"> - <topic href="ref/rwspref.html#rwspref" title="Web services preferences"/> - </entry> - </entry> - <entry keyword="Web services interoperability"> - <entry keyword="traffic compliance"> - <topic href="concepts/cwsiover.html#cwsiover" title="Web services interoperability (WS-I)"/> - </entry> - </entry> - <entry keyword="interoperability"> - <entry keyword="Web service traffic compliance"> - <topic href="concepts/cwsiover.html#cwsiover" title="Web services interoperability (WS-I)"/> - </entry> - </entry> - <entry keyword="WSI"> - <entry keyword="setting compliance"> - <topic href="tasks/twsicomply.html#twsicomply" title="Setting the level of WS-I compliance"/> - </entry> - </entry> - <entry keyword="top-down Web services"> - <entry keyword="creating"> - <topic href="concepts/cwstopdown.html#creatingtop-downwebservices" title="Creating top-down Web services"/> - </entry> - </entry> - <entry keyword="bottom-up Web services"> - <entry keyword="overview"> - <topic href="concepts/cwsbtmup.html#creatingbottom-upwebservices" title="Creating bottom-up Web services"/> - </entry> - </entry> -</index>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/plugin.properties b/docs/org.eclipse.jst.ws.doc.user/plugin.properties deleted file mode 100644 index 27cc7aa28..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/plugin.properties +++ /dev/null @@ -1,15 +0,0 @@ -############################################################################### -# Copyright (c) 2001, 2005 IBM Corporation and others. -# All rights reserved. This program and the accompanying materials -# are made available under the terms of the Eclipse Public License v1.0 -# which accompanies this distribution, and is available at -# http://www.eclipse.org/legal/epl-v10.html -# -# Contributors: -# IBM Corporation - initial API and implementation -############################################################################### -# NLS_MESSAGEFORMAT_VAR -# NLS_ENCODING=UTF-8 - -pluginName = Web Services UI -pluginProvider = Eclipse.org diff --git a/docs/org.eclipse.jst.ws.doc.user/plugin.xml b/docs/org.eclipse.jst.ws.doc.user/plugin.xml deleted file mode 100644 index 122acd02b..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/plugin.xml +++ /dev/null @@ -1,23 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> -<?eclipse version="3.0"?> -<?NLS TYPE="org.eclipse.help.toc"?> -<!-- /******************************************************************************* - * Copyright (c) 2000, 2007 IBM Corporation and others. - * All rights reserved. This program and the accompanying materials - * are made available under the terms of the Eclipse Public License v1.0 - * which accompanies this distribution, and is available at - * http://www.eclipse.org/legal/epl-v10.html - * - * Contributors: - * IBM Corporation - initial API and implementation - *******************************************************************************/ --> -<plugin> - - <extension point="org.eclipse.help.toc"> - <toc file="webservice_toc.xml" /> - <index path="index/"/> - </extension> - <extension point="org.eclipse.help.index"> - <index file="org.eclipse.jst.ws.doc.userindex.xml"/> - </extension> -</plugin>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita deleted file mode 100644 index 6fceb7d0e..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.dita +++ /dev/null @@ -1,55 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" - "reference.dtd"> -<reference id="rwsdl" xml:lang="en-us"> -<title>Web Services Description Language (WSDL) reference</title> -<shortdesc>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. </shortdesc> -<prolog><metadata> -<keywords><indexterm>WSDL<indexterm>reference</indexterm></indexterm><indexterm>Web -services<indexterm>WSDL reference</indexterm></indexterm></keywords> -</metadata></prolog> -<refbody> -<section><p>The concrete protocol and data format specifications for a particular -port type constitutes a reusable binding. A port is defined by associating -a network address with a reusable binding, and a collection of ports define -a service. Hence, a WSDL document uses the following elements in the definition -of network services:</p><ul> -<li> <uicontrol>Types</uicontrol>: a container for data type definitions using -some type system (such as XSD).</li> -<li> <uicontrol>Message</uicontrol>: an abstract, typed definition of the -data being communicated.</li> -<li> <uicontrol>Operation</uicontrol>: an abstract description of an action -supported by the service.</li> -<li> <uicontrol>Port Type</uicontrol>: an abstract set of operations supported -by one or more endpoints.</li> -<li> <uicontrol>Binding</uicontrol>: a concrete protocol and data format specification -for a particular port type. The binding is usually SOAP and the encoding and -data formatting regulations used (also known as the style) is usually literal -(this includes document/literal, and sometimes rpc/literal).</li> -<li> <uicontrol>Port</uicontrol>: a single endpoint defined as a combination -of a binding and a network address.</li> -<li> <uicontrol>Service</uicontrol>: a collection of related endpoints.</li> -</ul><p>For more information on WSDL, refer to </p><p><xref format="html" -href="http://www.w3.org/TR/wsdl" scope="external">www.w3.org/TR/wsdl</xref></p><p>The -various WSDL elements can be structured in many ways. It can be in one single -WSDL file or in mulitple WSDL files.</p></section> -</refbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../concepts/cws.dita"></link> -<link href="../concepts/cwsdl.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" -scope="peer"><linktext> Using the Web Services Explorer</linktext></link> -</linklist> -</related-links> -</reference> diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html deleted file mode 100644 index bade3f6a8..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/ref/rwsdl.html +++ /dev/null @@ -1,92 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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="reference" name="DC.Type" /> -<meta name="DC.Title" content="Web Services Description Language (WSDL) reference" /> -<meta name="abstract" content="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." /> -<meta name="description" content="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." /> -<meta content="WSDL, reference, Web services, WSDL reference" name="DC.subject" /> -<meta content="WSDL, reference, Web services, WSDL reference" name="keywords" /> -<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="../tasks/toverws.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rwsdl" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web Services Description Language (WSDL) reference</title> -</head> -<body id="rwsdl"><a name="rwsdl"><!-- --></a> - - -<h1 class="topictitle1">Web Services Description Language (WSDL) reference</h1> - - - -<div><p>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. </p> - -<div class="section"><p>The concrete protocol and data format specifications for a particular -port type constitutes a reusable binding. A port is defined by associating -a network address with a reusable binding, and a collection of ports define -a service. Hence, a WSDL document uses the following elements in the definition -of network services:</p> -<ul> -<li> <span class="uicontrol">Types</span>: a container for data type definitions using -some type system (such as XSD).</li> - -<li> <span class="uicontrol">Message</span>: an abstract, typed definition of the -data being communicated.</li> - -<li> <span class="uicontrol">Operation</span>: an abstract description of an action -supported by the service.</li> - -<li> <span class="uicontrol">Port Type</span>: an abstract set of operations supported -by one or more endpoints.</li> - -<li> <span class="uicontrol">Binding</span>: a concrete protocol and data format specification -for a particular port type. The binding is usually SOAP and the encoding and -data formatting regulations used (also known as the style) is usually literal -(this includes document/literal, and sometimes rpc/literal).</li> - -<li> <span class="uicontrol">Port</span>: a single endpoint defined as a combination -of a binding and a network address.</li> - -<li> <span class="uicontrol">Service</span>: a collection of related endpoints.</li> - -</ul> -<p>For more information on WSDL, refer to </p> -<p><a href="http://www.w3.org/TR/wsdl" target="_blank">www.w3.org/TR/wsdl</a></p> -<p>The -various WSDL elements can be structured in many ways. It can be in one single -WSDL file or in mulitple WSDL files.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><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><a href="../concepts/cwsdl.html" title="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.">Web Services Description Language (WSDL)</a></div></div> - -<div class="linklist"><strong>Related Tasks</strong><br /> - -<div><a href="../tasks/toverws.html"> Developing Web -services</a></div> -<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html"> Using the Web Services Explorer</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita deleted file mode 100644 index 73e8f3925..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.dita +++ /dev/null @@ -1,156 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE reference PUBLIC "-//OASIS//DTD DITA Reference//EN" - "reference.dtd"> -<reference id="rwspref" xml:lang="en-us"> -<title>Web services preferences</title> -<shortdesc>Before you begin developing Web services or clients, you can optimize -the workbench for Web services development by setting a variety of preferences.</shortdesc> -<prolog><metadata> -<keywords><indexterm>preferences<indexterm>Web services</indexterm></indexterm> -<indexterm>Web services<indexterm>preferences</indexterm></indexterm> -</keywords> -</metadata></prolog> -<refbody> -<section><p id="setprefmain">To set any of the Web services preferences, follow -these steps:<ol> -<li>Click <uicontrol>Window > Preferences</uicontrol> to open the Preferences -notebook.</li> -<li>Expand <uicontrol>Web services</uicontrol> or <uicontrol>Web and XML</uicontrol>, -and click the preference category that you want to set</li> -<li>Select the check boxes that you want to set as the default when creating -your Web service.</li> -<li>Click <uicontrol>OK</uicontrol> to apply the changes and close the Preferences -notebook.</li> -</ol>If you require more information on any of the options, select the option -and press <uicontrol>F1</uicontrol>.</p><p>Web services tools enable you -to define the following preferences:</p><dl><dlentry id="axisemitterpref"> -<dt>Axis Emitter</dt> -<dd>This page allows you to set the following preferences used when creating -or consuming Axis Web services.</dd> -<dd><b>WSDL2Java</b><ul> -<li>Generate code for all elements: By default, WSDL2Java only generates code -for those elements in the WSDL file that are referenced. For additional information -regarding how referencing works refer to the Axis reference guide: <xref href="http://ws.apache.org/axis/java/reference.html" -scope="external"></xref></li> -<li>Emits separate Helper classes for metadata: If you select this option -WSDL2Java will create a separate helper class that contains the metadata rather -than including it in the skeleton.</li> -<li>Prefers building beans to straight arrays for wrapped XML array types: -The default behavior is to map this XML construct: <codeblock><element name="array"> - <complexType> - <sequence> - <element name="item" type="xs:string"/> - </sequence> - </complexType> -</element></codeblock>to a Java String array (String[]). If you would rather -a specific JavaBean class (ArrayOfString) be generated for these types of -schemas, select this option. </li> -<li>Add scope to deploy.wsdd: This indicates how to deploy the server implementation. -Application uses one instance of the implementation class for all requests. -Request creates a new instance of the implementation class for each request. -Session creates a new instance of the implementation class for each session.</li> -<li>Timeout in seconds: The default is 45. Use -1 to disable the timeout.</li> -</ul></dd> -<dd><b>Java2WSDL</b><ul> -<li>Look for allowed methods in inherited class: If this option is specified, -the Java2WSDL parser will look into extended classes to determine the list -of methods to export into the WSDL file. </li> -<li>Analyze the service class for compliance to JAX-RPC before generating -code: If selected, the tools will examine the Java service class and its value -types to determine if it satisfies important requirements of the JAX-RPC specification.</li> -</ul></dd> -</dlentry><dlentry id="popupdialogselect"> -<dt>Popup Dialog Selection</dt> -<dd>The Dialogs preferences enable you to determine which dialog boxes that -you want to see when running popup actions. If you have disabled any of the -dialogs by selecting "Do not show this dialog again" on the first page of -a Web services wizard, you can undo your change by clearing the check box -beside the dialog that you have chosen to hide.</dd> -</dlentry><dlentry id="wsicompliance"> -<dt>Profile Compliance and Validation</dt> -<dd>The WS-I Compliance preferences allow you to select your level of compliance -with the WS-I Simple SOAP Binding Profile (SSBP) and WS-I Attachement Profile -(AP). Note: if you change the level of WS-I compliance while WS-I incompliances -are listed in the Task view, the Task view will not be automatically updated. -The workspace must be revalidated before the warnings will be removed from -the Task view. For more information on WS-I, refer to: <xref href="http://www.ws-i.org/" -scope="external"></xref></dd> -<dd>For validation preferences, you can choose whether or not WSDL files consumed -by the Web services wizards are validated, and whether or not the WSDL validation -must complete before the wizard will move to the next step.</dd> -</dlentry><dlentry id="projtopology"> -<dt>Project Topology</dt> -<dd>The Project Topology preferences allow you to:<ul> -<li>Select the default client project type that the Web services wizards will -create when generating a Web service client. You can also set the order in -which the client project types will be listed in the wizard. Note that this -selection is simply a default and an alternate project type can be selected -in the wizard.</li> -<li>Select whether you want to generate the Web service and the Web service -client in the same EAR project or different EAR projects. Generating the service -and client into different EAR projects can reduce the chance of conflicts -that occur when both exist in a single EAR project, but uses more system resources.</li> -</ul></dd> -</dlentry><dlentry id="resourcemanagement"> -<dt>Resource Management</dt> -<dd>The Resource Management preferences enable you to determine the file and -folder creation and overwriting defaults that you want to use when creating -your Web service.<ul> -<li>Overwrite files without warning: selecting this will allow the wizards -to overwrite any existing files in the workspace without prompting. If it -is not selected you will be prompted each time a file needs to be overwritten.</li> -<li>Create folders when necessary: selecting this enables the wizards to create -any required folders.</li> -<li>Check out files without warning: select to check out files without receiving -a warning message asking for confirmation.</li> -<li>Merge generated skeleton file: this check box is disabled by default. - If this check box is enabled, when a skeleton file of the same name already -exists in the workspace, the newly generated skeleton file will merge with -the existing skeleton file. Enable this to preserve code that you have already -modified in the existing skeleton files.<p>Note that when this preference -is enabled, if you change the return type of an interface, the resulting skeleton -file will have a method returning the type as defined in the new interface -but would have a method body from the original skeleton file (which would -be returning a different type). This will result in an compilation error -that the you will have to correct manually.</p></li> -</ul></dd> -</dlentry><dlentry id="scenariodefaults"> -<dt>Scenario Defaults</dt> -<dd>The Scenario Defaults preferences enable you to set the following scenario -defaults that you want to use when creating your Web service:<ul> -<li>which type of Web service and client you want to be selected by default.</li> -<li>which phases of the Web service lifecycle you want to complete in the -wizard.</li> -<li>if you want the Web Services Explorer to launch by default so that you -can publish your Web service to a UDDI registry.</li> -<li>if you want the Web service SOAP traffic routed through a TCP/IP monitor -so that you can monitor the SOAP packets and optionally test them for WS-I -compliance.</li> -</ul>Note that all these defaults can be overridden in the wizard.</dd> -</dlentry><dlentry id="serverandruntime"> -<dt>Server and Runtime</dt> -<dd>Select the server, Web service run-time environment, and J2EE version -that you want selected by default in the Web services wizard. Note that all -these defaults can be overridden in the wizard.</dd> -</dlentry><dlentry id="testfacilitydefaults"> -<dt>Test Facility Defaults</dt> -<dd>can select whether to have the wizard automatically launch a test facility, -and you can select your preferred type of test facility</dd> -</dlentry><dlentry id="wsdlfiles"> -<dt>WSDL files</dt> -<dd>When creating a WSDL file in the WSDL editor, you can set the default -target namespace. If you do not select to change the default, your WSDL file -will have http://tempuri.org as its target namespace.</dd> -</dlentry></dl></section> -</refbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../concepts/cwsinwsa.dita"></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../tasks/toverws.dita" scope="peer"><linktext> Developing Web -services</linktext></link> -</linklist> -</related-links> -</reference> diff --git a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html b/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html deleted file mode 100644 index 99609e3b9..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/ref/rwspref.html +++ /dev/null @@ -1,236 +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="Copyright (c) 2000, 2006 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2006" /> -<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="reference" name="DC.Type" /> -<meta name="DC.Title" content="Web services preferences" /> -<meta name="abstract" content="Before you begin developing Web services or clients, you can optimize the workbench for Web services development by setting a variety of preferences." /> -<meta name="description" content="Before you begin developing Web services or clients, you can optimize the workbench for Web services development by setting a variety of preferences." /> -<meta content="preferences, Web services" name="DC.subject" /> -<meta content="preferences, Web services" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../tasks/toverws.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="rwspref" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Web services preferences</title> -</head> -<body id="rwspref"><a name="rwspref"><!-- --></a> - - -<h1 class="topictitle1">Web services preferences</h1> - - - -<div><p>Before you begin developing Web services or clients, you can optimize -the workbench for Web services development by setting a variety of preferences.</p> - -<div class="section"><div class="p" id="rwspref__setprefmain"><a name="rwspref__setprefmain"><!-- --></a>To set any of the Web services preferences, follow -these steps:<ol> -<li>Click <span class="uicontrol">Window > Preferences</span> to open the Preferences -notebook.</li> - -<li>Expand <span class="uicontrol">Web services</span> or <span class="uicontrol">Web and XML</span>, -and click the preference category that you want to set</li> - -<li>Select the check boxes that you want to set as the default when creating -your Web service.</li> - -<li>Click <span class="uicontrol">OK</span> to apply the changes and close the Preferences -notebook.</li> - -</ol> -If you require more information on any of the options, select the option -and press <span class="uicontrol">F1</span>.</div> -<p>Web services tools enable you -to define the following preferences:</p> -<dl> -<dt class="dlterm"><a name="rwspref__axisemitterpref"><!-- --></a>Axis Emitter</dt> - -<dd>This page allows you to set the following preferences used when creating -or consuming Axis Web services.</dd> - -<dd class="ddexpand"><strong>WSDL2Java</strong><ul> -<li>Generate code for all elements: By default, WSDL2Java only generates code -for those elements in the WSDL file that are referenced. For additional information -regarding how referencing works refer to the Axis reference guide: <a href="http://ws.apache.org/axis/java/reference.html" target="_blank">http://ws.apache.org/axis/java/reference.html</a></li> - -<li>Emits separate Helper classes for metadata: If you select this option -WSDL2Java will create a separate helper class that contains the metadata rather -than including it in the skeleton.</li> - -<li>Prefers building beans to straight arrays for wrapped XML array types: -The default behavior is to map this XML construct: <pre><element name="array"> - <complexType> - <sequence> - <element name="item" type="xs:string"/> - </sequence> - </complexType> -</element></pre> -to a Java String array (String[]). If you would rather -a specific JavaBean class (ArrayOfString) be generated for these types of -schemas, select this option. </li> - -<li>Add scope to deploy.wsdd: This indicates how to deploy the server implementation. -Application uses one instance of the implementation class for all requests. -Request creates a new instance of the implementation class for each request. -Session creates a new instance of the implementation class for each session.</li> - -<li>Timeout in seconds: The default is 45. Use -1 to disable the timeout.</li> - -</ul> -</dd> - -<dd class="ddexpand"><strong>Java2WSDL</strong><ul> -<li>Look for allowed methods in inherited class: If this option is specified, -the Java2WSDL parser will look into extended classes to determine the list -of methods to export into the WSDL file. </li> - -<li>Analyze the service class for compliance to JAX-RPC before generating -code: If selected, the tools will examine the Java service class and its value -types to determine if it satisfies important requirements of the JAX-RPC specification.</li> - -</ul> -</dd> - - -<dt class="dlterm"><a name="rwspref__popupdialogselect"><!-- --></a>Popup Dialog Selection</dt> - -<dd>The Dialogs preferences enable you to determine which dialog boxes that -you want to see when running popup actions. If you have disabled any of the -dialogs by selecting "Do not show this dialog again" on the first page of -a Web services wizard, you can undo your change by clearing the check box -beside the dialog that you have chosen to hide.</dd> - - -<dt class="dlterm"><a name="rwspref__wsicompliance"><!-- --></a>Profile Compliance and Validation</dt> - -<dd>The WS-I Compliance preferences allow you to select your level of compliance -with the WS-I Simple SOAP Binding Profile (SSBP) and WS-I Attachement Profile -(AP). Note: if you change the level of WS-I compliance while WS-I incompliances -are listed in the Task view, the Task view will not be automatically updated. -The workspace must be revalidated before the warnings will be removed from -the Task view. For more information on WS-I, refer to: <a href="http://www.ws-i.org/" target="_blank">http://www.ws-i.org/</a></dd> - -<dd class="ddexpand">For validation preferences, you can choose whether or not WSDL files consumed -by the Web services wizards are validated, and whether or not the WSDL validation -must complete before the wizard will move to the next step.</dd> - - -<dt class="dlterm"><a name="rwspref__projtopology"><!-- --></a>Project Topology</dt> - -<dd>The Project Topology preferences allow you to:<ul> -<li>Select the default client project type that the Web services wizards will -create when generating a Web service client. You can also set the order in -which the client project types will be listed in the wizard. Note that this -selection is simply a default and an alternate project type can be selected -in the wizard.</li> - -<li>Select whether you want to generate the Web service and the Web service -client in the same EAR project or different EAR projects. Generating the service -and client into different EAR projects can reduce the chance of conflicts -that occur when both exist in a single EAR project, but uses more system resources.</li> - -</ul> -</dd> - - -<dt class="dlterm"><a name="rwspref__resourcemanagement"><!-- --></a>Resource Management</dt> - -<dd>The Resource Management preferences enable you to determine the file and -folder creation and overwriting defaults that you want to use when creating -your Web service.<ul> -<li>Overwrite files without warning: selecting this will allow the wizards -to overwrite any existing files in the workspace without prompting. If it -is not selected you will be prompted each time a file needs to be overwritten.</li> - -<li>Create folders when necessary: selecting this enables the wizards to create -any required folders.</li> - -<li>Check out files without warning: select to check out files without receiving -a warning message asking for confirmation.</li> - -<li>Merge generated skeleton file: this check box is disabled by default. - If this check box is enabled, when a skeleton file of the same name already -exists in the workspace, the newly generated skeleton file will merge with -the existing skeleton file. Enable this to preserve code that you have already -modified in the existing skeleton files.<p>Note that when this preference -is enabled, if you change the return type of an interface, the resulting skeleton -file will have a method returning the type as defined in the new interface -but would have a method body from the original skeleton file (which would -be returning a different type). This will result in an compilation error -that the you will have to correct manually.</p> -</li> - -</ul> -</dd> - - -<dt class="dlterm"><a name="rwspref__scenariodefaults"><!-- --></a>Scenario Defaults</dt> - -<dd>The Scenario Defaults preferences enable you to set the following scenario -defaults that you want to use when creating your Web service:<ul> -<li>which type of Web service and client you want to be selected by default.</li> - -<li>which phases of the Web service lifecycle you want to complete in the -wizard.</li> - -<li>if you want the Web Services Explorer to launch by default so that you -can publish your Web service to a UDDI registry.</li> - -<li>if you want the Web service SOAP traffic routed through a TCP/IP monitor -so that you can monitor the SOAP packets and optionally test them for WS-I -compliance.</li> - -</ul> -Note that all these defaults can be overridden in the wizard.</dd> - - -<dt class="dlterm"><a name="rwspref__serverandruntime"><!-- --></a>Server and Runtime</dt> - -<dd>Select the server, Web service run-time environment, and J2EE version -that you want selected by default in the Web services wizard. Note that all -these defaults can be overridden in the wizard.</dd> - - -<dt class="dlterm"><a name="rwspref__testfacilitydefaults"><!-- --></a>Test Facility Defaults</dt> - -<dd>can select whether to have the wizard automatically launch a test facility, -and you can select your preferred type of test facility</dd> - - -<dt class="dlterm"><a name="rwspref__wsdlfiles"><!-- --></a>WSDL files</dt> - -<dd>When creating a WSDL file in the WSDL editor, you can set the default -target namespace. If you do not select to change the default, your WSDL file -will have http://tempuri.org as its target namespace.</dd> - -</dl> -</div> - -</div> - -<div> -<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="../concepts/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/tasks/toverws.dita b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.dita deleted file mode 100644 index 6e045f5f9..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.dita +++ /dev/null @@ -1,54 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="toverws" xml:lang="en-us"> -<title>Developing Web services</title> -<shortdesc>Use Web services tools to discover, create, and publish Web services -that are created from <tm tmclass="special" tmowner="Sun Microsystems, Inc." -tmtype="tm" trademark="Java">Java</tm> 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 <tm tmclass="special" -tmowner="Sun Microsystems, Inc." tmtype="tm" trademark="Java">Java</tm> bean -or EJB).</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>creating<indexterm>overview</indexterm></indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>In this release, the development path that you would typically -follow to create and publish a Web service is as follows:</p></context> -<steps> -<step><cmd>Create a Web project.</cmd></step> -<step><cmd>Create or import an artifact to be turned into a Web service.</cmd> -</step> -<step><cmd>Create a Web service.</cmd></step> -<step><cmd>Publish a business entity.</cmd></step> -<step><cmd>Publish a Web service.</cmd></step> -</steps> -<result><p>For instructions on performing these tasks, refer to the list of -related topics at the end of this topic.</p><p>Web tools assist you in developing -Web applications that you can configure as a Web service. Web applications -are developed in a Web project, and Server tools allow you to use the server -test environment to test and deploy your Web services.</p></result> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../concepts/cws.dita" scope="local"><linktext>Web services overview</linktext> -</link> -<link href="../concepts/cwsinwsa.dita" scope="local"><linktext>Tools for Web -services development</linktext></link> -<link href="../concepts/cwsbtmup.dita" scope="local"><linktext>Creating bottom-up -Web services</linktext></link> -<link href="../concepts/cwstopdown.dita" scope="local"><linktext>Creating -top-down Web services</linktext></link> -</linklist> -<linklist><title>Related Tasks</title> -<link href="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.dita" scope="peer"> -<linktext>Creating a new WSDL file</linktext></link> -<link href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.dita" -scope="peer"><linktext>Publishing Web services and business entities</linktext> -</link> -</linklist> -</related-links> -</task> diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html b/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html deleted file mode 100644 index ce452dff3..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/tasks/toverws.html +++ /dev/null @@ -1,87 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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="task" name="DC.Type" /> -<meta name="DC.Title" content="Developing Web services" /> -<meta name="abstract" content="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)." /> -<meta name="description" content="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)." /> -<meta content="Web services, creating, overview" name="DC.subject" /> -<meta content="Web services, creating, overview" name="keywords" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cws.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsinwsa.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwsbtmup.html" /> -<meta scheme="URI" name="DC.Relation" content="../concepts/cwstopdown.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html" /> -<meta scheme="URI" name="DC.Relation" content="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="toverws" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Developing Web services</title> -</head> -<body id="toverws"><a name="toverws"><!-- --></a> - - -<h1 class="topictitle1">Developing Web services</h1> - - - -<div><p>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).</p> - -<div class="section"><p>In this release, the development path that you would typically -follow to create and publish a Web service is as follows:</p> -</div> - -<ol> -<li><span>Create a Web project.</span></li> - -<li><span>Create or import an artifact to be turned into a Web service.</span> -</li> - -<li><span>Create a Web service.</span></li> - -<li><span>Publish a business entity.</span></li> - -<li><span>Publish a Web service.</span></li> - -</ol> - -<div class="section"><p>For instructions on performing these tasks, refer to the list of -related topics at the end of this topic.</p> -<p>Web tools assist you in developing -Web applications that you can configure as a Web service. Web applications -are developed in a Web project, and Server tools allow you to use the server -test environment to test and deploy your Web services.</p> -</div> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><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><a href="../concepts/cwsinwsa.html" title="">Tools for Web -services development</a></div> -<div><a href="../concepts/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><a href="../concepts/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="../../org.eclipse.wst.wsdl.ui.doc.user/tasks/tcrtwsdl.html">Creating a new WSDL file</a></div> -<div><a href="../../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tuddiexp.html">Publishing Web services and business entities</a></div></div> -</div> - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita deleted file mode 100644 index 46216b673..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.dita +++ /dev/null @@ -1,67 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE task PUBLIC "-//OASIS//DTD DITA Task//EN" - "task.dtd"> -<task id="twsicomply" xml:lang="en-us"> -<title>Setting the level of WS-I compliance</title> -<shortdesc>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 -are not WS-I compliant.</shortdesc> -<prolog><metadata> -<keywords><indexterm>Web services<indexterm>interoperability compliance</indexterm></indexterm> -<indexterm>WSI<indexterm>setting compliance</indexterm></indexterm> -</keywords> -</metadata></prolog> -<taskbody> -<context><p>You can set the level of compliance for either the Basic Profile -and the Simple SOAP Binding Profile, or for the Attachments Profile. You can -select from three levels of compliance with WS-I specifications:</p><ul> -<li>Require WS-I compliance - this level prevents you from creating a non-compliant -Web service.</li> -<li>Suggest WS-I compliance - this level allows you to create a non-compliant -Web service, but provides a visible warning stating how the service is non-compliant.</li> -<li>Ignore WS-I compliance - this level allows you to create a non-compliant -Web service and does not notify you of non-compliance.</li> -</ul><p>You can set the level of WS-I compliance at the workspace level, or -at the project level.</p></context> -</taskbody> -<task id="sdgfsdgs" xml:lang="en-us"> -<title>Set the level of WS-I compliance for the workspace</title> -<taskbody> -<context><p>To set the level of WS-I compliance for the workspace:</p></context> -<steps> -<step><cmd>From the <b>Window</b> menu, select <b>Preferences</b>.</cmd> -</step> -<step><cmd>Select <b>Web Services</b> from the component tree on the left-hand -side of the panel.</cmd></step> -<step><cmd>Under <b>Profile Compliance and Validation</b>, select the level -of compliance you want from the drop-down lists.</cmd></step> -<step><cmd>Click <b>Apply</b>, then click <b>OK</b>.</cmd></step> -</steps> -</taskbody> -</task> -<task id="xvgdsgfsg" xml:lang="en-us"> -<title>Set the level of WS-I compliance for a project</title> -<taskbody> -<context><p>To set the level of WS-I compliance for a project:</p></context> -<steps> -<step><cmd>In the Project Navigator, right click and select <b>Properties</b>.</cmd> -</step> -<step><cmd>Select <b>Profile Compliance and Validation</b> from the component -tree on the left-hand side of the panel.</cmd></step> -<step><cmd>Select the level of compliance you want from the drop-down lists, -or select to have the project share the same level of WS-I compliance as the -workspace</cmd></step> -<step><cmd>Click <b>Apply</b>, then click <b>OK</b>.</cmd></step> -</steps> -</taskbody> -<related-links> -<linklist><title>Related Concepts</title> -<link href="../concepts/cwsiover.dita" scope="local"></link> -</linklist> -</related-links> -</task> -</task> diff --git a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html b/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html deleted file mode 100644 index fabf06f10..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/tasks/twsicomply.html +++ /dev/null @@ -1,114 +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="Copyright (c) 2000, 2007 IBM Corporation and others. All rights reserved. This program and the accompanying materials are made available under the terms of the Eclipse Public License v1.0 which accompanies this distribution, and is available at http://www.eclipse.org/legal/epl-v10.html. Contributors: IBM Corporation - initial API and implementation" /> -<meta name="DC.rights.owner" content="(C) Copyright 2000, 2007" /> -<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="task" name="DC.Type" /> -<meta name="DC.Title" content="Setting the level of WS-I compliance" /> -<meta name="abstract" content="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 are not WS-I compliant." /> -<meta name="description" content="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 are not WS-I compliant." /> -<meta content="Web services, interoperability compliance, WSI, setting compliance" name="DC.subject" /> -<meta content="Web services, interoperability compliance, WSI, setting compliance" name="keywords" /> -<meta content="XHTML" name="DC.Format" /> -<meta content="twsicomply" name="DC.Identifier" /> -<meta content="en-us" name="DC.Language" /> -<link href="../../org.eclipse.wst.doc.user/common.css" type="text/css" rel="stylesheet" /> -<title>Setting the level of WS-I compliance</title> -</head> -<body id="twsicomply"><a name="twsicomply"><!-- --></a> - - -<h1 class="topictitle1">Setting the level of WS-I compliance</h1> - - - -<div><p>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 -are not WS-I compliant.</p> - -<div class="section"><p>You can set the level of compliance for either the Basic Profile -and the Simple SOAP Binding Profile, or for the Attachments Profile. You can -select from three levels of compliance with WS-I specifications:</p> -<ul> -<li>Require WS-I compliance - this level prevents you from creating a non-compliant -Web service.</li> - -<li>Suggest WS-I compliance - this level allows you to create a non-compliant -Web service, but provides a visible warning stating how the service is non-compliant.</li> - -<li>Ignore WS-I compliance - this level allows you to create a non-compliant -Web service and does not notify you of non-compliance.</li> - -</ul> -<p>You can set the level of WS-I compliance at the workspace level, or -at the project level.</p> -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="sdgfsdgs"><a name="sdgfsdgs"><!-- --></a> -<h2 class="topictitle2">Set the level of WS-I compliance for the workspace</h2> - -<div> -<div class="section"><p>To set the level of WS-I compliance for the workspace:</p> -</div> - -<ol> -<li><span>From the <strong>Window</strong> menu, select <strong>Preferences</strong>.</span> -</li> - -<li><span>Select <strong>Web Services</strong> from the component tree on the left-hand -side of the panel.</span></li> - -<li><span>Under <strong>Profile Compliance and Validation</strong>, select the level -of compliance you want from the drop-down lists.</span></li> - -<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li> - -</ol> - -</div> - -</div> - -<div class="nested1" xml:lang="en-us" id="xvgdsgfsg"><a name="xvgdsgfsg"><!-- --></a> -<h2 class="topictitle2">Set the level of WS-I compliance for a project</h2> - -<div> -<div class="section"><p>To set the level of WS-I compliance for a project:</p> -</div> - -<ol> -<li><span>In the Project Navigator, right click and select <strong>Properties</strong>.</span> -</li> - -<li><span>Select <strong>Profile Compliance and Validation</strong> from the component -tree on the left-hand side of the panel.</span></li> - -<li><span>Select the level of compliance you want from the drop-down lists, -or select to have the project share the same level of WS-I compliance as the -workspace</span></li> - -<li><span>Click <strong>Apply</strong>, then click <strong>OK</strong>.</span></li> - -</ol> - -</div> - -<div> -<div class="linklist"><strong>Related Concepts</strong><br /> - -<div><a href="../concepts/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> -</div> - - -</body> -</html>
\ No newline at end of file diff --git a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap deleted file mode 100644 index 8ea946c29..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.ditamap +++ /dev/null @@ -1,91 +0,0 @@ -<?xml version="1.0" encoding="utf-8"?> -<!--Arbortext, Inc., 1988-2005, v.4002--> -<!DOCTYPE map PUBLIC "-//OASIS//DTD DITA Map//EN" - "map.dtd"> -<map id="wsmaintoc" title="wsmaintoc"> -<topicref href="concepts/cws.dita" navtitle="Web services development"> -<topicref href="concepts/cwsstandards.dita" navtitle="Web services standards" -scope="local"> -<topicref href="concepts/cwsdl.dita" navtitle="Web Services Description Language (WSDL)"> -<topicref href="ref/rwsdl.dita" navtitle="Web Services Description Language (WSDL) reference"> -</topicref> -</topicref> -<topicref href="concepts/csoap.dita" navtitle="SOAP"></topicref> -<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.dita" -navtitle="Universal Description, Discovery, and Integration (UDDI)" scope="peer"> -<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.dita" -navtitle="Relationship between UDDI and WSDL" scope="peer"></topicref> -</topicref> -<topicref href="concepts/cwsil.dita" navtitle="Web Services Inspection Language (WSIL)"> -<topicref href="concepts/cwsilud.dita" navtitle="Relationship between UDDI and WSIL"> -</topicref> -</topicref> -<topicref href="concepts/cjaxrpc.dita" navtitle="JAX-RPC"></topicref> -<topicref href="concepts/cjsr109.dita" navtitle="JSR 109 and JSR 921"></topicref> -</topicref> -<topicref navtitle="Workspace and tools"> -<topicref href="concepts/cwsinwsa.dita" navtitle="Tools for Web services development" -scope="local"> -<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.dita" -navtitle="Creating Web services with the Apache Axis run-time environment" -scope="peer"></topicref> -</topicref> -<topicref navtitle="Configuring your workspace"> -<topicref href="ref/rwspref.dita" navtitle="Setting Web services preferences" -scope="local"></topicref> -<topicref href="concepts/cwsiover.dita" navtitle="WS-I compliance" scope="local"> -<topicref href="tasks/twsicomply.dita" navtitle="Setting the level of WS-I compliance" -scope="local"></topicref> -</topicref> -<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.dita" -navtitle="Creating an Apache Tomcat server and Web project" scope="peer"> -</topicref> -</topicref> -</topicref> -</topicref> -<topicref navtitle="Importing and creating resources used by Web services"> -<navref mapref="../org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.ditamap"/> -</topicref> -<topicref href="tasks/toverws.dita" navtitle="Creating Web services"> -<topicref href="concepts/cwstopdown.dita" navtitle="Top-down Web services development" -scope="local"> -<topicgroup> -<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.dita" -navtitle="Creating a Web service and Java bean skeleton from WSDL" scope="peer"> -</topicref> -</topicgroup> -</topicref> -<topicref href="concepts/cwsbtmup.dita" navtitle="Bottom-up Web services development" -scope="local"> -<topicgroup> -<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.dita" -navtitle="Creating a Web service from a Java bean" scope="peer"></topicref> -</topicgroup> -</topicref> -<topicref navtitle="Creating Web service clients"> -<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.dita" -navtitle="Discovering and importing a Web service" scope="peer"></topicref> -<topicref href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.dita" -navtitle="Generating a Java client proxy from a WSDL document using the Axis run-time environment" -scope="peer"></topicref> -<anchor id="extending_ws_client_creation"/></topicref> -<navref mapref="../org.eclipse.wst.command.env.doc.user/wsaxisant_toc.ditamap"/> -</topicref> -<topicref navtitle="Testing and validating Web services"> -<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.dita" -navtitle="Testing WSDL documents and Web services with the WSDL Explorer" -scope="peer"></topicref> -<topicref href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.dita" navtitle="Validating WSDL" -scope="peer"></topicref> -<topicref href="../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.dita" navtitle="Testing Web services with the TCP/IP Monitor" -scope="peer"> -<topicref href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.dita" navtitle="Validating WS-I compliance of Web service SOAP traffic" -scope="peer"></topicref> -</topicref> -</topicref> -<topicref navtitle="Publishing Web services"> -<navref mapref="../org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.ditamap"/> -<topicref href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.dita" -navtitle="Generating WSIL" scope="peer"></topicref> -</topicref> -</map> diff --git a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml b/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml deleted file mode 100644 index b5d76c30c..000000000 --- a/docs/org.eclipse.jst.ws.doc.user/webservice_toc.xml +++ /dev/null @@ -1,62 +0,0 @@ -<?xml version="1.0" encoding="UTF-8"?> - -<?NLS TYPE="org.eclipse.help.toc"?> - -<toc label="wsmaintoc" topic="concepts/cws.html"> -<topic label="Web services overview" href="concepts/cws.html"> -<topic label="Web services standards" href="concepts/cwsstandards.html"> -<topic label="Web Services Description Language (WSDL)" href="concepts/cwsdl.html"> -<topic label="Web Services Description Language (WSDL) reference" href="ref/rwsdl.html"/> -</topic> -<topic label="SOAP" href="concepts/csoap.html"/> -<topic label="Universal Description, Discovery, and Integration (UDDI)" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cuddi.html"> -<topic label="Relationship between UDDI and WSDL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/concepts/cwsdlud.html"/> -</topic> -<topic label="Web Services Inspection Language (WSIL)" href="concepts/cwsil.html"> -<topic label="Relationship between UDDI and WSIL" href="concepts/cwsilud.html"/> -</topic> -<topic label="JAX-RPC" href="concepts/cjaxrpc.html"/> -<topic label="JSR 109 and JSR 921- Implementing Enterprise Web services" href="concepts/cjsr109.html"/> -</topic> -<topic label="Workspace and tools"> -<topic label="Tools for Web services development" href="concepts/cwsinwsa.html"> -<topic label="Creating Web services with the Apache Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/concepts/caxistover.html"/> -</topic> -<topic label="Configuring your workspace"> -<topic label="Web services preferences" href="ref/rwspref.html"/> -<topic label="Web services interoperability (WS-I)" href="concepts/cwsiover.html"> -<topic label="Setting the level of WS-I compliance" href="tasks/twsicomply.html"/> -</topic> -<topic label="Creating an Apache Tomcat server and Web project" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/ttomcatserv.html"/> -</topic> -</topic> -</topic> -<topic label="Importing and creating resources used by Web services"> -<link toc="../org.eclipse.wst.wsdl.ui.doc.user/wswsdleditort_toc.xml"/> -</topic> -<topic label="Developing Web services" href="tasks/toverws.html"> -<topic label="Creating top-down Web services" href="concepts/cwstopdown.html"> -<topic label="Creating a Web service and Java bean skeleton from WSDL" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsklwsdla.html"/> -</topic> -<topic label="Creating bottom-up Web services" href="concepts/cwsbtmup.html"> -<topic label="Creating a Web service from a Java bean" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/twsbeana.html"/> -</topic> -<topic label="Creating Web service clients"> -<topic label="Discovering and importing a Web service" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tdiscov.html"/> -<topic label="Generating a Java client proxy from a WSDL document using the Axis run-time environment" href="../org.eclipse.jst.ws.axis.ui.doc.user/tasks/tsampappa.html"/> -<anchor id="extending_ws_client_creation"/> -</topic> -<link toc="../org.eclipse.wst.command.env.doc.user/wsaxisant_toc.xml"/> -</topic> -<topic label="Testing and validating Web services"> -<topic label="Testing WSDL documents and Web services with the WSDL Explorer" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/ttestwsdl.html"/> -<topic label="Validating WSDL" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsdlval.html"/> -<topic label="Testing Web services with the TCP/IP Monitor" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/tmonitor.html"> -<topic label="Validating WS-I compliance of Web service SOAP traffic" href="../org.eclipse.wst.wsi.ui.doc.user/tasks/twsival.html"/> -</topic> -</topic> -<topic label="Publishing Web services"> -<link toc="../org.eclipse.jst.ws.consumption.ui.doc.user/wsconsumptiont_toc.xml"/> -<topic label="Generating WSIL" href="../org.eclipse.jst.ws.consumption.ui.doc.user/tasks/tgenwsil.html"/> -</topic> -</toc> |
