Author: alessio.soldano(a)jboss.com Date: 2011-12-19 06:20:38 -0500 (Mon, 19 Dec 2011) New Revision: 15427 Modified: stack/cxf/trunk/modules/dist/src/main/doc/chapter-4-JAX_WS_Tools.xml stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml Log: Updating doc Modified: stack/cxf/trunk/modules/dist/src/main/doc/chapter-4-JAX_WS_Tools.xml =================================================================== --- stack/cxf/trunk/modules/dist/src/main/doc/chapter-4-JAX_WS_Tools.xml 2011-12-19 10:47:31 UTC (rev 15426) +++ stack/cxf/trunk/modules/dist/src/main/doc/chapter-4-JAX_WS_Tools.xml 2011-12-19 11:20:38 UTC (rev 15427) @@ -722,7 +722,7 @@ &lt;plugin&gt; &lt;groupId&gt;org.jboss.ws.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-jaxws-tools-plugin&lt;/artifactId&gt; - &lt;version&gt;1.0.0.GA&lt;/version&gt; + &lt;version&gt;1.1.0.GA&lt;/version&gt; &lt;configuration&gt; &lt;wsdls&gt; &lt;wsdl&gt;${basedir}/test.wsdl&lt;/wsdl&gt; @@ -746,7 +746,7 @@ &lt;plugin&gt; &lt;groupId&gt;org.jboss.ws.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-jaxws-tools-plugin&lt;/artifactId&gt; - &lt;version&gt;1.0.0.GA&lt;/version&gt; + &lt;version&gt;1.1.0.GA&lt;/version&gt; &lt;configuration&gt; &lt;wsdls&gt; &lt;wsdl&gt;${basedir}/test.wsdl&lt;/wsdl&gt; @@ -778,7 +778,7 @@ &lt;plugin&gt; &lt;groupId&gt;org.jboss.ws.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-jaxws-tools-plugin&lt;/artifactId&gt; - &lt;version&gt;1.0.0.GA&lt;/version&gt; + &lt;version&gt;1.1.0.GA&lt;/version&gt; &lt;configuration&gt; &lt;wsdls&gt; &lt;wsdl&gt;${basedir}/test.wsdl&lt;/wsdl&gt; @@ -795,6 +795,33 @@ &lt;/plugins&gt; &lt;/build&gt;</programlisting> </informalexample> + <para> + Plugin stack dependencyThe plugin itself does not have an explicit dependency to a JBossWS stack, as it's meant for being used with implementations of any supported version of the + <emphasis role="italics">JBossWS SPI</emphasis> + . So the user is expected to set a dependency in his own + <code>pom.xml</code> + to the desired + <emphasis role="italics">JBossWS</emphasis> + stack version. The plugin will rely on the that for using the proper tooling. + </para> + <informalexample> + <programlisting>&lt;dependencies&gt; + &lt;dependency&gt; + &lt;groupId&gt;org.jboss.ws.cxf&lt;/groupId&gt; + &lt;artifactId&gt;jbossws-cxf-client&lt;/artifactId&gt; + &lt;version&gt;4.0.0.GA&lt;/version&gt; + &lt;/dependency&gt; +&lt;/dependencies&gt;</programlisting> + </informalexample> + <tip> + <para> + Be careful when using this plugin with the Maven War Plugin as that include any project dependency into the generated application war archive. You might want to set + <code>&lt;scope&gt;provided&lt;/scope&gt;</code> + for the + <emphasis role="italics">JBossWS</emphasis> + stack dependency to avoid that. + </para> + </tip> </section> </section> <section id="sid-3866762_wsconsume-AntTask"> @@ -1242,7 +1269,7 @@ &lt;plugin&gt; &lt;groupId&gt;org.jboss.ws.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-jaxws-tools-plugin&lt;/artifactId&gt; - &amp;lt;version&amp;gt;@pom.version(a)&amp;lt;/version&amp;gt; + &lt;version&gt;1.1.0.GA&lt;/version&gt; &lt;configuration&gt; &lt;verbose&gt;true&lt;/verbose&gt; &lt;endpointClass&gt;org.jboss.test.ws.plugins.tools.wsprovide.TestEndpoint&lt;/endpointClass&gt; @@ -1266,7 +1293,7 @@ &lt;plugin&gt; &lt;groupId&gt;org.jboss.ws.plugins&lt;/groupId&gt; &lt;artifactId&gt;maven-jaxws-tools-plugin&lt;/artifactId&gt; - &amp;lt;version&amp;gt;@pom.version(a)&amp;lt;/version&amp;gt; + &lt;version&gt;1.1.0.GA&lt;/version&gt; &lt;configuration&gt; &lt;verbose&gt;true&lt;/verbose&gt; &lt;endpointClass&gt;org.jboss.test.ws.plugins.tools.wsprovide.TestEndpoint2&lt;/endpointClass&gt; @@ -1283,6 +1310,33 @@ &lt;/plugins&gt; &lt;/build&gt;</programlisting> </informalexample> + <para> + Plugin stack dependencyThe plugin itself does not have an explicit dependency to a JBossWS stack, as it's meant for being used with implementations of any supported version of the + <emphasis role="italics">JBossWS SPI</emphasis> + . So the user is expected to set a dependency in his own + <code>pom.xml</code> + to the desired + <emphasis role="italics">JBossWS</emphasis> + stack version. The plugin will rely on the that for using the proper tooling. + </para> + <informalexample> + <programlisting>&lt;dependencies&gt; + &lt;dependency&gt; + &lt;groupId&gt;org.jboss.ws.cxf&lt;/groupId&gt; + &lt;artifactId&gt;jbossws-cxf-client&lt;/artifactId&gt; + &lt;version&gt;4.0.0.GA&lt;/version&gt; + &lt;/dependency&gt; +&lt;/dependencies&gt;</programlisting> + </informalexample> + <tip> + <para> + Be careful when using this plugin with the Maven War Plugin as that include any project dependency into the generated application war archive. You might want to set + <code>&lt;scope&gt;provided&lt;/scope&gt;</code> + for the + <emphasis role="italics">JBossWS</emphasis> + stack dependency to avoid that. + </para> + </tip> </section> </section> <section id="sid-3866758_wsprovide-AntTask"> Modified: stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml =================================================================== --- stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml 2011-12-19 10:47:31 UTC (rev 15426) +++ stack/cxf/trunk/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml 2011-12-19 11:20:38 UTC (rev 15427) @@ -384,7 +384,7 @@ </section> <section id="sid-3866793"> - <title>Addressing</title> + <title>WS-Addressing</title> <para> JBoss Web Services inherits full WS-Addressing capabilities from the underlying Apache CXF implementation. Apache CXF provides support for 2004-08 and <ulink url="http://www.w3.org/TR/ws-addr-core/">1.0</ulink> @@ -465,7 +465,7 @@ </section> <section id="sid-3866793_WS-Addressing-WSAddressingPolicy"> - <title>Addressing Policy</title> + <title>WS-Addressing Policy</title> <para>The WS-Addressing support is also perfectly integrated with the Apache CXF WS-Policy engine.</para> <para> This basically means that the WSDL contract generation for code-first endpoint deployment is policy-aware: users can annotate endpoints with the @@ -575,10 +575,10 @@ </section> <section id="sid-3866795"> - <title>Security</title> + <title>WS-Security</title> <section id="sid-3866795_WS-Security-"> - <title>Security overview</title> + <title>WS-Security overview</title> <para> WS-Security provides the means to secure your services beyond transport level protocols such as <emphasis role="italics">HTTPS</emphasis> @@ -664,7 +664,7 @@ <para>Recent versions of Apache CXF, however, introduced support for WS-Security Policy, which aims at moving most of the security configuration into the service contract (through policies), so that clients can easily be configured almost completely automatically from that. This way users do not need to manually deal with configuring / installing the required interceptors; the Apache CXF WS-Policy engine internally takes care of that instead.</para> <section id="sid-3866795_WS-Security-WSSecurityPolicysupport"> - <title>Security Policy support</title> + <title>WS-Security Policy support</title> <para> WS-SecurityPolicy describes the actions that are required to securely communicate with a service advertised in a given WSDL contract. The WSDL bindings / operations reference WS-Policy fragments with the security requirements to interact with the service. The <ulink url="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/v1.3/ws-secu... specification</ulink> @@ -1668,7 +1668,7 @@ </section> <section id="sid-3866797"> - <title>Reliable Messaging</title> + <title>WS-Reliable Messaging</title> <para> JBoss Web Services inherits full WS-Reliable Messaging capabilities from the underlying Apache CXF implementation. At the time of writing, Apache CXF provides support for the <ulink url="http://schemas.xmlsoap.org/ws/2005/02/rm/">WS-Reliable Messaging 1.0</ulink>