From riftsaw-commits at lists.jboss.org Tue Jun 1 07:25:01 2010 Content-Type: multipart/mixed; boundary="===============5438645029765638723==" MIME-Version: 1.0 From: riftsaw-commits at lists.jboss.org To: riftsaw-commits at lists.jboss.org Subject: [riftsaw-commits] riftsaw SVN: r688 - trunk/docs/docbook/userguide/src/main/module. Date: Tue, 01 Jun 2010 07:25:01 -0400 Message-ID: <201006011125.o51BP1TC029247@svn01.web.mwc.hst.phx2.redhat.com> --===============5438645029765638723== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Author: objectiser Date: 2010-06-01 07:25:01 -0400 (Tue, 01 Jun 2010) New Revision: 688 Modified: trunk/docs/docbook/userguide/src/main/module/wsconfig.xml Log: RIFTSAW-75 - added some documentation for how to provide cxf configuration = details in the BPEL deployment. Modified: trunk/docs/docbook/userguide/src/main/module/wsconfig.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/docs/docbook/userguide/src/main/module/wsconfig.xml 2010-05-31 12= :23:39 UTC (rev 687) +++ trunk/docs/docbook/userguide/src/main/module/wsconfig.xml 2010-06-01 11= :25:01 UTC (rev 688) @@ -90,4 +90,226 @@ = = +
+ Apache CXF Configuration + = + + RiftSaw integrates with JBossWS, using the JAX-WS standard API, t= o support the + following web service stacks: JBossWS native, Metro and Apache CX= F. This section + explains how RiftSaw deployed BPEL processes can include addition= al configuration + specifically applicable to the Apache CXF web service stack - and= is therefore + only relevant if the JBossAS application server has been configur= ed to use this + stack. See the Getting Started Guide for inf= ormation on how to + switch to the Apache CXF stack when installing RiftSaw. + + = + + This section will explain how web service endpoints, whether serv= er (i.e. representing + the BPEL process) or client (i.e. being used to invoke external w= eb services), are + configured using the Apache CXF configuration format. It will als= o discuss reasons + why you may wish to do this additional CXF specific configuration= . However, for further + information on how to configure CXF, and the features that it off= ers, the reader is + referred to the Apache CXF website http://cxf.apache.org. + + = +
+ Configuring the Server endpoint + = + + To create a CXF configuration that will be used by the RiftSaw we= b service provider + (i.e. the server), it is simply a case of placing a file called + jbossws-cxf.xml into the root folder of the = BPEL deployment + (along side the deployment descriptor). + + = + + This is the same filename as used by jbossws-cxf, when deploying = a web service based + on the use of JAXWS annotations. An example of the file content i= s: + + = + + + = + + + + = + + + = + + + + + + = + + + + = + + + = + + + + + + + + + + + + + + + + + + = + = + + ]]> + + + + This example configures the web service to use username token and digi= tal signature + authentication. + = +
+ = +
+ Configuring the Client endpoint + = + + When configuring client endpoints, representing web services invo= ked by a BPEL + process, the configuration is currently separated into different = files on a per + port basis - similar to the approach used by the Axis2 ODE integr= ation. + + = + + The file name is of the form jbossws-cxf-{portname_loca= l_part}.xml, + where the portname_local_part represents the= local part of + the portname of the web service being invoked. For example, if th= e WSDL for the invoked + web service is: + + = + + + + ... + + + + ... + + + + ]]> + + = + + then the CXF configuration file would be jbossws-cxf-Sec= ureHelloWorldPort.xml. + + = + + The CXF configuration information within this file is associated w= ith the CXF bus. For + example: + + = + + + + + + + = + + + = + + + + + + + = + + + + = + + + = + + + + + + = + + + + + + + + + + + + + ]]> + + + + This example configures the web service client to use username token a= nd digital signature + authentication. + = +
+
--===============5438645029765638723==--