[jbossws-commits] JBossWS SVN: r15860 - in stack/cxf/branches/jbossws-cxf-4.0.x: modules/dist/src/main/doc and 1 other directory.

Author: alessio.soldano(a)jboss.com Date: 2012-03-05 05:52:38 -0500 (Mon, 05 Mar 2012) New Revision: 15860 Modified: stack/cxf/branches/jbossws-cxf-4.0.x/ stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/Revision_History.xml stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-3-JAX_WS_User_Guide.xml stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-6-JBoss_Modules.xml Log: Merged revisions 15859 via svnmerge from https://svn.jboss.org/repos/jbossws/stack/cxf/trunk ....... r15859 | alessio.soldano(a)jboss.com | 2012-03-05 11:50:14 +0100 (Mon, 05 Mar 2012) | 2 lines Updating doc ....... Property changes on: stack/cxf/branches/jbossws-cxf-4.0.x ___________________________________________________________________ Modified: svnmerge-integrated - https://svn.jboss.org/repos/jbossws/stack/cxf/trunk:1-15635,15658,15668,1... + https://svn.jboss.org/repos/jbossws/stack/cxf/trunk:1-15635,15658,15668,1... Modified: svn:mergeinfo - /stack/cxf/branches/asoldano:14032-14050,14068 /stack/cxf/trunk:15658,15668,15674-15675,15682,15695-15697,15708,15711,15713,15719,15723-15730,15738,15743,15748,15750-15751,15754-15757,15765-15766,15768,15773,15780-15781,15784,15794,15806-15808,15824,15835 + /stack/cxf/branches/asoldano:14032-14050,14068 /stack/cxf/trunk:15658,15668,15674-15675,15682,15695-15697,15708,15711,15713,15719,15723-15730,15738,15743,15748,15750-15751,15754-15757,15765-15766,15768,15773,15780-15781,15784,15794,15806-15808,15824,15835,15859 Modified: stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/Revision_History.xml =================================================================== --- stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/Revision_History.xml 2012-03-05 10:50:14 UTC (rev 15859) +++ stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/Revision_History.xml 2012-03-05 10:52:38 UTC (rev 15860) @@ -32,6 +32,20 @@ </simplelist> </revdescription> </revision> + <revision> + <revnumber>4.0.2</revnumber> + <date>Mon Mar 05 2012</date> + <author> + <firstname>Alessio</firstname> + <surname>Soldano</surname> + <email&gt;alessio.soldano(a)jboss.com&lt;/email&gt; + </author> + <revdescription> + <simplelist> + <member>JBossWS-CXF 4.0.2 documentation</member> + </simplelist> + </revdescription> + </revision> </revhistory> </simpara> </appendix> Modified: stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-3-JAX_WS_User_Guide.xml =================================================================== --- stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-3-JAX_WS_User_Guide.xml 2012-03-05 10:50:14 UTC (rev 15859) +++ stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-3-JAX_WS_User_Guide.xml 2012-03-05 10:52:38 UTC (rev 15860) @@ -360,7 +360,7 @@ <section id="sid-3866716_JAX-WSUserGuide-WebServiceRefcustomization"> <title>WebServiceRef customization</title> - <para>Starting from jboss-5.0.x we offer a number of overrides and extensions to the WebServiceRef annotation. These include</para> + <para>We offer a number of overrides and extensions to the WebServiceRef annotation. These include</para> <itemizedlist> <listitem> <para>define the port that should be used to resolve a container-managed port</para> @@ -409,8 +409,9 @@ </informalexample> <para> For details please see - <emphasis role="italics">service-ref_5_0.dtd</emphasis> - in the jboss docs directory. + <emphasis role="italics"> + <ulink url="http://www.jboss.org/j2ee/dtd/service-ref_5_0.dtd">serv... + </emphasis> </para> </section> </section> Modified: stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml =================================================================== --- stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml 2012-03-05 10:50:14 UTC (rev 15859) +++ stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-5-Advanced_User_Guide.xml 2012-03-05 10:52:38 UTC (rev 15860) @@ -38,7 +38,7 @@ <title>Server configuration options</title> <para>The configuration options are part of the webservices subsystem section of the JBoss Application Server 7 domain model.</para> <informalexample> - <programlisting>&lt;subsystem xmlns="urn:jboss:domain:webservices:1.0" xmlns:javaee="http://java.sun.com/xml/ns/javaee" + <programlisting>&lt;subsystem xmlns="urn:jboss:domain:webservices:1.1" xmlns:javaee="http://java.sun.com/xml/ns/javaee" xmlns:jaxwsconfig="urn:jboss:jbossws-jaxws-config:4.0"&gt; &lt;wsdl-host&gt;localhost&lt;/wsdl-host&gt; &lt;modify-wsdl-address&gt;true&lt;/modify-wsdl-address&gt; @@ -68,12 +68,12 @@ When the application server is bound to multiple addresses or non-trivial real-world network architectures cause request for different external addresses to hit the same endpoint, a static rewrite of the soap:address may not be enough. JBossWS allows for both the soap:address in the wsdl and the wsdl address in the console to be rewritten with the host use in the client request. This way, users always get the right wsdl address assuming they're connecting to an instance having the endpoint they're looking for. To trigger this behaviour, the <emphasis role="italics">jbossws.undefined.host</emphasis> value has to be specified for the - <emphasis role="italics">webServiceHost</emphasis> - attribute. + <emphasis role="italics">wsdl-host</emphasis> + element. </para> <informalexample> - <programlisting>&lt;property name="webServiceHost"&gt;jbossws.undefined.host&lt;/property&gt; -&lt;property name="modifySOAPAddress"&gt;true&lt;/property&gt;</programlisting> + <programlisting>&lt;wsdl-host&gt;jbossws.undefined.host&lt;/wsdl-host&gt; +&lt;modify-wsdl-address&gt;true&lt;/modify-wsdl-address&gt;</programlisting> </informalexample> <para>Of course, when a confidential transport address is required, the addresses are always rewritten using https protocol and the port currently configured for the https/ssl connector.</para> </section> Modified: stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-6-JBoss_Modules.xml =================================================================== --- stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-6-JBoss_Modules.xml 2012-03-05 10:50:14 UTC (rev 15859) +++ stack/cxf/branches/jbossws-cxf-4.0.x/modules/dist/src/main/doc/chapter-6-JBoss_Modules.xml 2012-03-05 10:52:38 UTC (rev 15860) @@ -54,10 +54,6 @@ <programlisting>Dependencies: com.sun.xml.bind services export</programlisting> </informalexample> </section> - </section> - <section id="sid-4784150_JBossModules-"> - - <title/> <section id="sid-4784150_JBossModules-UsingApacheCXF"> <title>Using Apache CXF</title> @@ -71,10 +67,14 @@ </informalexample> <para>However, please note that would not come with any JBossWS-CXF customizations nor additional extensions. For this reason, and generally speaking for simplifying user configuration, a client side aggregation module is available with all the WS dependencies users might need.</para> </section> + <section id="sid-4784150_JBossModules-ClientsideWSaggregationmodule"> + + <title>Client side WS aggregation module</title> + </section> </section> - <section id="sid-4784150_JBossModules-ClientsideWSaggregationmodule"> + <section id="sid-4784150_JBossModules-"> - <title>Client side WS aggregation module</title> + <title/> <para>Whenever you simply want to use all the JBoss Web Services feature/functionalities, you can set a dependency to the convenient client module.</para> <informalexample> <programlisting>Dependencies: org.jboss.ws.cxf.jbossws-cxf-client services export</programlisting> @@ -116,5 +116,19 @@ module. So either create that manually in the application server or use the JBossWS-CXF installation scripts for doing that. </para> </section> + <section id="sid-4784150_JBossModules-Annotationscanning"> + + <title>Annotation scanning</title> + <para> + The application server uses an annotation index for detecting JAX-WS endpoints in user deployments. When declaring WS endpoints whose class belongs to a different module (for instance referring that in the + <code>web.xml</code> + descriptor), be sure to have an + <code>annotations</code> + type dependency in place. Without that, your endpoints would simply be ignored as they won't appear as annotated classes to the webservices subsystem. + </para> + <informalexample> + <programlisting>Dependencies: org.foo annotations</programlisting> + </informalexample> + </section> </section> </chapter>