[savara-commits] savara SVN: r109 - tools/eclipse/trunk/docs/gettingstartedguide/src/main/module.

[do-not-reply at jboss.org]

Author: objectiser
Date: 2009-12-05 19:00:41 -0500 (Sat, 05 Dec 2009)
New Revision: 109

Modified:
   tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml
Log:
Added message and schema validation.

Modified: tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml
===================================================================
--- tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml	2009-12-05 23:23:10 UTC (rev 108)
+++ tools/eclipse/trunk/docs/gettingstartedguide/src/main/module/architecture.xml	2009-12-06 00:00:41 UTC (rev 109)
@@ -10,8 +10,51 @@
 	<section>
 		<title>Define Information Model</title>
 
+		<para>
+		One of the stages within the architecture phase is to define the information model
+		for the message types associated with the messages exchanges between the
+		interacting participants.
+		</para>
+		
+		<para>
+		This involves defining message schema for each example message. The schema could
+		already exist and be reused, it could be based on existing schema and just need
+		to be upgraded to support new requirements, or it may need to be defined from
+		scratch.
+		</para>
+		
+		<para>
+		An example of a schema associated with the purchasing model is the
+		<filename>store.xsd</filename> shown here:
+		</para>
+
 		<informalexample>
   			<programlisting role="XML" ><![CDATA[
+<?xml version="1.0" encoding="UTF-8"?>
+<schema xmlns="http://www.w3.org/2001/XMLSchema" 
+		targetNamespace="http://www.jboss.org/examples/store" 
+		xmlns:tns="http://www.jboss.org/examples/store" 
+		elementFormDefault="qualified">
+
+    <element name="BuyRequest" type="tns:StoreType"></element>
+    <element name="BuyConfirmed" type="tns:StoreType"></element>
+    <element name="BuyFailed" type="tns:StoreType"></element>
+
+    <complexType name="StoreType">
+    	<attribute name="id" type="string"></attribute>
+    </complexType>
+</schema>
+	 		]]></programlisting>
+		</informalexample>
+		
+		<para>
+		Once the schema has been defined, then the example messages need to be updated
+		to reference the schema, as shown in the following <filename>BuyRequest.xml</filename>
+		example message:
+		</para>
+		
+		<informalexample>
+  			<programlisting role="XML" ><![CDATA[
 <tns:BuyRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
 			xmlns:tns="http://www.jboss.org/examples/store" 
 			xsi:schemaLocation="http://www.jboss.org/examples/store store.xsd " 
@@ -23,7 +66,16 @@
 			<title>Validating Example Messages against Schema</title>
 
 			<para>
+			Once the association between example messages and the schema has been
+			established, it is possible to validate the messages against the
+			schema.
 			</para>
+			
+			<para>
+			For information on how to use the validation capabilities within
+			Eclipse, please read the
+			<ulink url="http://www.eclipse.org/webtools/community/tutorials/XMLValidation/XMLValidationTutorial.html">Eclipse XML Validation Tutorial</ulink>.
+			</para>
 		</section>
 	</section>