Author: objectiser Date: 2011-02-18 17:41:34 -0500 (Fri, 18 Feb 2011) New Revision: 698 Modified: branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/master.xml branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/installation.xml branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/overview.xml branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml branches/experimental/2.0.x/docs/samplesguide/src/main/en-US/module/servicevalidator.xml branches/experimental/2.0.x/docs/userguide/src/main/en-US/module/conversation-validation.xml Log: Update docs for version 2. Modified: branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/master.xml =================================================================== --- branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/master.xml 2011-02-18 21:28:04 UTC (rev 697) +++ branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/master.xml 2011-02-18 22:41:34 UTC (rev 698) @@ -17,6 +17,8 @@ <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/architecture.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/serviceanalysisdesign.xml"/> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/servicedev.xml"/> +<!-- <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/tap.xml"/> +--> <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="module/runtimevalidation.xml"/> </book> Modified: branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/installation.xml =================================================================== --- branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/installation.xml 2011-02-18 21:28:04 UTC (rev 697) +++ branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/installation.xml 2011-02-18 22:41:34 UTC (rev 698) @@ -20,12 +20,12 @@ </orderedlist> <para> - The pre-requisites for the SAVARA Service Validator are: + The pre-requisites for the SAVARA JBoss server integration are: </para> <orderedlist> <listitem>JBossAS (5.1.0.GA or higher) <ulink url="http://www.jboss.org/jbossas">http://www.jboss.org/jbos... <listitem>JBossAS (4.8 or higher) <ulink url="http://www.jboss.org/jbossesb">http://www.jboss.org/jbo... - <listitem>SAVARA (version 1.1.0 or higher), available from <ulink url="http://www.jboss.org/savara/downloads">http://www.jboss... + <listitem>SAVARA (version 2.0.0 or higher), available from <ulink url="http://www.jboss.org/savara/downloads">http://www.jboss... </orderedlist> </section> @@ -90,7 +90,7 @@ </orderedlist> <para> - The installation instructions for the SAVARA Service Validator are: + The installation instructions for the SAVARA JBoss server integration are: </para> <orderedlist> <listitem> Modified: branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/overview.xml =================================================================== --- branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/overview.xml 2011-02-18 21:28:04 UTC (rev 697) +++ branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/overview.xml 2011-02-18 22:41:34 UTC (rev 698) @@ -27,8 +27,10 @@ <listitem>Generation of documentation based on the choreography</listitem> <listitem>Generation of service implementation using WS-BPEL</listitem> <listitem>Generation of service interfaces using WSDL</listitem> +<!-- <listitem>Conformance checking a WS-BPEL service implementation against a choreography</listitem> - <listitem>Runtime validation of an ESB service against a choreography description</listitem> +--> + <listitem>Runtime validation of JBossWS (Native) and ESB services against a choreography description</listitem> </itemizedlist> </chapter> Modified: branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml =================================================================== --- branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2011-02-18 21:28:04 UTC (rev 697) +++ branches/experimental/2.0.x/docs/gettingstartedguide/src/main/en-US/module/runtimevalidation.xml 2011-02-18 22:41:34 UTC (rev 698) @@ -7,7 +7,7 @@ <note> <para> Before you can deploy and run the runtime validation example, you will - need to install the SAVARA Validator module for JBoss. + need to install the SAVARA JBoss server integration. </para> </note> @@ -43,16 +43,16 @@ </para> <section> - <title>Service Validator Configuration</title> + <title>Server Configuration</title> <para> - The service validator configuration is defined using specific annotation, that is associated + The runtime validation configuration is defined using specific annotation, that is associated with the 'exchange details' components (contained within interactions), within the choreography description. </para> <para> - To view the pre-configured service validator configuration defined for the Purchasing + To view the pre-configured runtime service validator configuration defined for the Purchasing example, edit the <filename>PurchaseGoods.cdm</filename> file, navigate to the <emphasis>Choreography Flows</emphasis> tab and then select the <emphasis>Choreography->Edit Annotations</emphasis> menu item associated with the first @@ -65,7 +65,7 @@ <para> This will display the annotation editor, with the single configured annotation called - 'validator'. This annotation defines the information required for the Service Validator + 'validator'. This annotation defines the information required for the runtime validation to monitor this specific message exchange (e.g. the JMS destination on which the message will be passed, or in this case the Service Name for the target Web Service). @@ -87,7 +87,7 @@ <para> Once the annotations have been defined for all relevant 'exchange details' components in the choreography description, the choreography file can be copied to the - <filename>${JBossAS}/server/default/deploy/savara-validator-jboss.sar/models</filename> + <filename>${JBossAS}/server/default/deploy/savara-jboss.sar/models</filename> folder in the JBossAS environment. The service validator configuration for the <emphasis>purchasing</emphasis> example has been preconfigured to be deployed as part of the installation procedure. @@ -95,9 +95,9 @@ <note> <para> - If the <filename>savara-validator-jboss.sar/validator-config.xml</filename> within the JBossAS + If the <filename>savara-jboss.sar/validator-config.xml</filename> within the JBossAS environment is modified, or choreography description files added, removed or updated within - the <filename>savara-validator-jboss.sar/models</filename> sub-folder, then the changes will + the <filename>savara-jboss.sar/models</filename> sub-folder, then the changes will automatically be detected and used to re-configure the service validators without having to restart the server. </para> @@ -376,7 +376,7 @@ <itemizedlist> <listitem> - From the <filename>${SAVARA}/samples/trailblazer</filename> folder, execute the + From the <filename>${SAVARA}/samples/jbossesb/trailblazer</filename> folder, execute the following command to deploy the example to the ESB: <emphasis role="bold">ant deploy-error-client</emphasis>. </listitem> Modified: branches/experimental/2.0.x/docs/samplesguide/src/main/en-US/module/servicevalidator.xml =================================================================== --- branches/experimental/2.0.x/docs/samplesguide/src/main/en-US/module/servicevalidator.xml 2011-02-18 21:28:04 UTC (rev 697) +++ branches/experimental/2.0.x/docs/samplesguide/src/main/en-US/module/servicevalidator.xml 2011-02-18 22:41:34 UTC (rev 698) @@ -39,7 +39,7 @@ environment. </listitem> <listitem> -Update the <filename>${SAVARA}/samples/trailblazer/trailblazer.properties</filename> +Update the <filename>${SAVARA}/samples/jbossesb/trailblazer/trailblazer.properties</filename> <para> Update the <property>file.bank.monitored.directory</property> and <property>file.output.directory</property> properties. These are folders used by the File Based Bank, @@ -76,7 +76,7 @@ <listitem> <para> In the Eclipse environment, select the popup menu associated with the <filename>trailblazer.cdm</filename> -file, and choose the <emphasis>Choreography->Monitor</emphasis> menu item. +file, and choose the <emphasis>Savara->Monitor</emphasis> menu item. </para> <imageobject> @@ -133,7 +133,7 @@ <para> Compared to command of <emphasis role="bold">ant deploy</emphasis>, basically, we have just updated the following code in - <emphasis role="bold">${SAVARA}/samples/trailblazer/client/src/org/jboss/soa/esb/samples/trailblazer/loanbroker/LoanBroker.java</emphasis> file. + <emphasis role="bold">${SAVARA}/samples/jbossesb/trailblazer/client/src/org/jboss/soa/esb/samples/trailblazer/loanbroker/LoanBroker.java</emphasis> file. </para> <para> In the following code within the <emphasis role="bold">processLoanRequest</emphasis> @@ -149,14 +149,14 @@ <para> Issue further loan requests, remembering to change the quote reference each time, until a Credit Check result of between 4 and 6 inclusive occurs, which will result in an out of sequence message - being reported (in red) to the Choreography Monitor + being reported (in red) to the Savara Monitor </para> <note> <para> It is currently a requirement that the choreography used within the Choreography Monitor is the same as the description used to locally monitor the services - (i.e. within the savara-validator-jbossesb.esb/models directory). + (i.e. within the savara-jbossesb.esb/models directory). </para> </note> Modified: branches/experimental/2.0.x/docs/userguide/src/main/en-US/module/conversation-validation.xml =================================================================== --- branches/experimental/2.0.x/docs/userguide/src/main/en-US/module/conversation-validation.xml 2011-02-18 21:28:04 UTC (rev 697) +++ branches/experimental/2.0.x/docs/userguide/src/main/en-US/module/conversation-validation.xml 2011-02-18 22:41:34 UTC (rev 698) @@ -39,7 +39,7 @@ is through the use of a global filter registered in the <filename>standard-jaxws-client-config.xml</filename> and <filename>standard-jaxws-endpoint-config.xml</filename> files. - These files are located in the <emphasis>$JBossAS/server/default/deployers/jbossws.deployter/META-INF</emphasis> + These files are located in the <emphasis>$JBossAS/server/default/deployers/jbossws.deployer/META-INF</emphasis> folder. </para> @@ -56,8 +56,8 @@ <javaee:handler-chain> <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings> <javaee:handler> - <javaee:handler-name>SAVARA JBossWS-Native Client Validator Interceptor</javaee:handler-name> - <javaee:handler-class>org.savara.validator.jbosswsnative.JBossWSNativeClientInterceptor</javaee:handler-class> + <javaee:handler-name>SAVARA JBossWS-Native Client Interceptor</javaee:handler-name> + <javaee:handler-class>org.savara.integration.jbosswsnative.JBossWSNativeClientInterceptor</javaee:handler-class> </javaee:handler> </javaee:handler-chain> </pre-handler-chains> @@ -90,8 +90,8 @@ <javaee:handler-chain> <javaee:protocol-bindings>##SOAP11_HTTP</javaee:protocol-bindings> <javaee:handler> - <javaee:handler-name>SAVARA JBossWS-Native Service Validator Interceptor</javaee:handler-name> - <javaee:handler-class>org.savara.validator.jbosswsnative.JBossWSNativeServerInterceptor</javaee:handler-class> + <javaee:handler-name>SAVARA JBossWS-Native Service Interceptor</javaee:handler-name> + <javaee:handler-class>org.savara.integration.jbosswsnative.JBossWSNativeServerInterceptor</javaee:handler-class> </javaee:handler> </javaee:handler-chain> </pre-handler-chains> @@ -119,7 +119,7 @@ <properties name="filters"> ... <property name="org.jboss.soa.esb.filter.10" - value="org.savara.validator.jbossesb.ValidatorFilter"/> + value="org.savara.integration.jbossesb.JBossESBInterceptor"/> </properties> ]]></programlisting> </informalexample> @@ -136,7 +136,7 @@ <para> The information concerning which destinations will be validated, and to which model/role they relate, can be explicitly defined within the <emphasis>validator-config.xml</emphasis> - file, contained within the <emphasis>savara-validator-jbossesb.esb</emphasis> bundle. + file, contained within the <emphasis>savara-jbossesb.esb</emphasis> bundle. </para> <para> @@ -209,7 +209,7 @@ <emphasis>LoanBrokerParticipant</emphasis> defined within the choreography description model found in the file <filename>TrailBlazer.cdm</filename>, which will be located within the <filename>models</filename> folder contained within the - <emphasis>savara-validator-jboss.sar</emphasis> bundle. + <emphasis>savara-jboss.sar</emphasis> bundle. </para> <para> The elements contained within the 'service' element define the <emphasis>input</emphasis> and @@ -311,7 +311,7 @@ When all of the relevant 'exchange details' components have been configured with a <emphasis>validator</emphasis> annotation, defining the EPR to be validated, then the choreography description file can be copied into the - <filename>savara-validator-jboss.sar/models</filename> folder. This will cause + <filename>savara-jboss.sar/models</filename> folder. This will cause the validation mechanism to derive the configuration information from the choreography description model, and begin validating the defined destinations against that choreography description model.