[jboss-cvs] JBossAS SVN: r92836 - projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US.
jboss-cvs-commits at lists.jboss.org
jboss-cvs-commits at lists.jboss.org
Wed Aug 26 10:47:02 EDT 2009
Author: richard.opalka at jboss.com
Date: 2009-08-26 10:47:02 -0400 (Wed, 26 Aug 2009)
New Revision: 92836
Modified:
projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml
Log:
[JBPAPP-2620] replacing obsolete links
Modified: projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml
===================================================================
--- projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2009-08-26 14:10:30 UTC (rev 92835)
+++ projects/docs/enterprise/5.0/Administration_And_Configuration_Guide/en-US/Web_Services.xml 2009-08-26 14:47:02 UTC (rev 92836)
@@ -327,11 +327,11 @@
<screen>http://yourhost:8080/jbossws/services</screen>
<para>
-It is also possible to generate the abstract contract off line using jboss tools. For details of that see <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e741">#Top Down (Using wsconsume)</ulink></para>
+It is also possible to generate the abstract contract off line using jboss tools. For details of that see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">#Top Down (Using wsconsume)</ulink></para>
</section>
<section>
<title>EJB3 Stateless Session Bean (SLSB)</title>
- <para>The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e213"># Plain old Java Object (POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC progamming model.</para>
+ <para>The JAX-WS programming model support the same set of annotations on EJB3 stateless session beans as on <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Plain_old_Java_Object_POJO"># Plain old Java Object (POJO)</ulink> endpoints. EJB-2.1 endpoints are supported using the JAX-RPC progamming model.</para>
<programlisting role="JAVA">
@Stateless
@Remote(EJB3RemoteInterface.class)
@@ -367,7 +367,7 @@
</formalpara>
<programlisting> <![CDATA[
http://yourhost:8080/jbossws/services]]> </programlisting>
- <para>It is also possible to generate the abstract contract offline using JbossWS tools. For details of that please see <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e741">#Top Down (Using wsconsume)</ulink></para>
+ <para>It is also possible to generate the abstract contract offline using JbossWS tools. For details of that please see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">#Top Down (Using wsconsume)</ulink></para>
</section>
<section>
<title>Endpoint Provider</title>
@@ -451,7 +451,7 @@
...
}</programlisting>
- <para>Section <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e401">#Dynamic Proxy</ulink> explains how to obtain a port from the service and how to invoke an operation on the port. If you need to work with the XML payload directly or with the XML representation of the entire SOAP message, have a look at <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e468">#Dispatch</ulink>.</para>
+ <para>Section <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dynamic_Proxy">#Dynamic Proxy</ulink> explains how to obtain a port from the service and how to invoke an operation on the port. If you need to work with the XML payload directly or with the XML representation of the entire SOAP message, have a look at <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Dispatch">#Dispatch</ulink>.</para>
<formalpara>
<title>Dynamic case</title>
<para>In the dynamic case, when nothing is generated, a web service client uses <literal>Service.create</literal> to create Service instances, the following code illustrates this process.</para>
@@ -465,14 +465,12 @@
</section>
<section>
<title>Handler Resolver</title>
- <para>JAX-WS provides a flexible plug-in framework for message processing modules, known as handlers, that may be used to extend the capabilities of a JAX-WS runtime system. <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e528">Handler Framework</ulink> describes the handler framework in detail. A <classname>Service</classname> instance provides access to a <classname>HandlerResolver</classname> via a pair of <methodname>getHandlerResolver</methodname> and <methodname>setHandlerResolver</methodname> methods that may be used to configure a set of handlers on a per-service, per-port or per-protocol binding basis.</para>
+ <para>JAX-WS provides a flexible plug-in framework for message processing modules, known as handlers, that may be used to extend the capabilities of a JAX-WS runtime system. <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Handler_Framework">Handler Framework</ulink> describes the handler framework in detail. A <classname>Service</classname> instance provides access to a <classname>HandlerResolver</classname> via a pair of <methodname>getHandlerResolver</methodname> and <methodname>setHandlerResolver</methodname> methods that may be used to configure a set of handlers on a per-service, per-port or per-protocol binding basis.</para>
<para>When a <classname>Service</classname> instance is used to create a proxy or a <classname>Dispatch</classname> instance then the handler resolver currently registered with the service is used to create the required handler chain. Subsequent changes to the handler resolver configured for a <classname>Service</classname> instance do not affect the handlers on previously created proxies, or <classname>Dispatch</classname> instances.</para>
- <!--<para>[TODO] <ulink url="http://jira.jboss.org/jira/browse/JBWS-1512">(JBWS-1512) Provide a sample for Service HandlerResolver</ulink></para>-->
</section>
<section>
<title>Executor</title>
<para><classname>Service</classname> instances can be configured with a <classname>java.util.concurrent.Executor</classname>. The executor will then be used to invoke any asynchronous callbacks requested by the application. The <methodname>setExecutor</methodname> and <methodname>getExecutor</methodname> methods of <classname>Service</classname> can be used to modify and retrieve the executor configured for a service.</para>
- <!--<para>[TODO] <ulink url="http://jira.jboss.org/jira/browse/JBWS-1513">(JBWS-1513) Provide a sample for Service Executor</ulink></para>-->
</section>
</section>
<section>
@@ -505,8 +503,8 @@
{
...
}</programlisting>
-<para>The <emphasis>Service Endpoint Interface</emphasis> (SEI) is usually generated using tools. For details see <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e741">Top Down (Using wsconsume)</ulink>.</para>
-<para>A generated static <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e330"><classname>Service</classname></ulink> usually also offers typed methods to get ports. These methods also return dynamic proxies that implement the SEI.</para>
+<para>The <emphasis>Service Endpoint Interface</emphasis> (SEI) is usually generated using tools. For details see <ulink url="http://www.jboss.org/community/wiki/JBossWS-JAX-WSTools#TopDown_Using_wsconsume">Top Down (Using wsconsume)</ulink>.</para>
+<para>A generated static <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Service"><classname>Service</classname></ulink> usually also offers typed methods to get ports. These methods also return dynamic proxies that implement the SEI.</para>
<programlisting role="JAVA">
@WebServiceClient(name = "TestEndpointService", targetNamespace = "http://org.jboss.ws/wsref",
wsdlLocation = "http://localhost.localdomain:8080/jaxws-samples-webserviceref?wsdl")
@@ -678,7 +676,7 @@
</section>
<section>
<title>Common API</title>
- <para>This sections describes concepts that apply equally to <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e208">#Web Service Endpoints</ulink> and <ulink url="http://labs.jboss.com/jbossws/docs/jaxws_userguide-2.0/index.html#d0e327">#Web Service Clients</ulink></para>
+ <para>This sections describes concepts that apply equally to <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Endpoints">#Web Service Endpoints</ulink> and <ulink url="http://www.jboss.org/community/wiki/JBossWS-UserGuide#Web_Service_Clients">#Web Service Clients</ulink></para>
<section>
<title>Handler Framework</title>
<para>The handler framework is implemented by a JAX-WS protocol binding in both client and server side runtimes. Proxies, and Dispatch instances, known collectively as binding providers, each use protocol bindings to bind their abstract functionality to specific protocols.</para>
More information about the jboss-cvs-commits
mailing list