Author: jeff.yuchang Date: 2010-07-15 00:11:21 -0400 (Thu, 15 Jul 2010) New Revision: 873 Modified: branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/wsconfig.xml Log: * Added jdbc configuration explanation and remove the 'Metro' as we don't support it. Modified: branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml =================================================================== --- branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-07-14 21:32:17 UTC (rev 872) +++ branches/RiftSaw-2.1.x/docs/docbook/gettingstartedguide/src/main/module/installation.xml 2010-07-15 04:11:21 UTC (rev 873) @@ -42,7 +42,7 @@ <para> If you have previously installed RiftSaw-2.0.0.Final, then you will need to drop the database schema due to changes in the ODE db schema for version 1.3.4. This can be achieved using the scripts in the - <filename>${riftsaw}/db/sql</filename> folder, or running: + <filename>${riftsaw}/db/sql</filename> folder, or configure the jdbc properties file in <filename>${riftsaw}/db/jdbc</filename> and running: </para> <para> ant -D{database} drop.riftsaw.schema Modified: branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/wsconfig.xml =================================================================== --- branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/wsconfig.xml 2010-07-14 21:32:17 UTC (rev 872) +++ branches/RiftSaw-2.1.x/docs/docbook/userguide/src/main/module/wsconfig.xml 2010-07-15 04:11:21 UTC (rev 873) @@ -95,7 +95,7 @@ <para> RiftSaw integrates with JBossWS, using the JAX-WS standard API, to support the - following web service stacks: JBossWS native, Metro and Apache CXF. This section + following web service stacks: JBossWS native and Apache CXF. This section explains how RiftSaw deployed BPEL processes can include additional configuration specifically applicable to the Apache CXF web service stack - and is therefore only relevant if the JBossAS application server has been configured to use this