From: Suzanne Duce <s.duce@dundee.ac.uk>
Date: Thu, 3 Apr 2014 09:05:57 +0000 (+0100)
Subject: JWS-86 edited the text and added googlecode link which wasn't active.
X-Git-Url: http://source.jalview.org/gitweb/?a=commitdiff_plain;h=5d67503042d7fbc96b0970855e3fdf0a756ea3f8;p=jabaws.git

JWS-86 edited the text and added googlecode link which wasn't active.
---

diff --git a/website/man_server_dev.html b/website/man_server_dev.html
index 1c3354f..791709e 100644
--- a/website/man_server_dev.html
+++ b/website/man_server_dev.html
@@ -67,9 +67,9 @@
   <p><a href="full_javadoc/index.html">Complete</a> javadoc - for developers who want to use JABAWS framework and use Engines and Executables directly</p>
   <h4><a name="thesrc" id="thesrc"></a>The source code</h4>
 <p><a name="svn">Publicly available Git repository:</a><a href="http://source.jalview.org/gitweb/?p=jabaws.git;a=summary">http://source.jalview.org/gitweb/?p=jabaws.git;a=summary</a></p>
-<p>Another publicly available JABAWS repository containing the code for each JABAWS public release is located at https://jabaws.googlecode.com/ </p>
+<p>Another publicly available JABAWS repository, containing the code for each JABAWS public release, is located at <a href="https://jabaws.googlecode.com">jabaws.googlecode.com</a></p>
 <p>The repositories contain a complete JABAWS <a href="http://www.eclipse.org">Eclipse</a> project. </p>
-<p>Of cause If you want to make a modification to the source code you would need to generate distributives yourself. To do that first generate JAX-WS artifacts using <span class="hightlight">build-server</span> task from <span class="hightlight">wsbuild.xml</span> ant script, than you could use build.xml tasks to generate any of the distributives you need. </p>
+<p>Of course if you want to make a modification to the source code you would need to generate distributives yourself. To do that, first generate JAX-WS artifacts using <span class="hightlight">build-server</span> task from <span class="hightlight">wsbuild.xml</span> ant script, then you could use build.xml tasks to generate any of the distributives you need. </p>
 <h4><a name="projstruct" id="projstruct"></a>Structure of the project</h4>
 <ul>
 	<li><span class="directory">binaries</span>	contains native executables e.g. clustalw</li>
@@ -104,7 +104,7 @@
 
 <h4><a name="runtests" id="runtests"></a>Running tests</h4>
 <p>
-JABAWS uses TestNG framework for testing. The test results for the JABAWS package offered for download can be found here: 
+JABAWS uses TestNG framework for testing. The test results for the JABAWS package offered for download can be found at: 
 <a href="http://www.compbio.dundee.ac.uk/user/www-jws2/tests/index.html">Test Results</a><br/>
 JABAWS uses <a href="http://testng.org/doc/index.html">TestNG</a> for testing. There is a TestNG plugin available for Eclipse 
 which has functionality similar to JUnit. However, no plugins are necessary to run the test cases, as testng jar is supplied 
@@ -206,9 +206,9 @@ those that depends on the cluster.</p>
 		<p>Create a testcase suit for your wrapper in <span class="hightlight">testsrc</span> and run the test cases.</p>
 	</li><li>
 		<p>Create parser for the output files of your executable. Suggested location 
-		compbio.data.sequence.SequenceUtil </p>
+		compbio.data.sequence.SequenceUtil . </p>
 	</li><li>
-		<p>Test the parser</p>
+		<p>Test the parser.</p>
 	</li><li>
 		<p>Decide which web services interfaces your executable is going to match. For example 
 		if the executable output can be represented as SequenceAnnotation then SequenceAnnotation 
@@ -218,7 +218,7 @@ those that depends on the cluster.</p>
 		implement a web service which confirms to it within a webservices source folder. </p>
 	</li><li> 
 		<p>Register web service in <span class="hightlight">WEB-INF/web.xml</span> 
-		and <span class="hightlight">WEB-INF/sun-jaxws.xml</span></p>
+		and <span class="hightlight">WEB-INF/sun-jaxws.xml</span> .</p>
 	</li><li> 
 		<p>Add generated wsdl to wsbuild.xml ant script to generate the stubs.</p>
 	</li><li>
@@ -226,12 +226,12 @@ those that depends on the cluster.</p>
 		that JAXB cannot serialize some of your new data structures. Add appropriate annotations to your data types.
 		Also check that: </p>
 		<ul>
-		<li>you do not have interfaces to serialize, since JAXB cannot serialize them;</li>
-		<li>you have a default no args constructor (can be private if you do not need it);</li>
-		<li>JAXB cannot serialize Java Map class, use a custom data structure instead;</li>
-		<li>Enum cannot be serialized as its abstract class (do not confuse with enum which is fine);</li>
+		<li>you do not have interfaces to serialize, since JAXB cannot serialize them</li>
+		<li>you have a default no args constructor (can be private if you do not need it)</li>
+		<li>JAXB cannot serialize Java Map class, use a custom data structure instead</li>
+		<li>Enum cannot be serialized as its abstract class (do not confuse with enum which is fine)</li>
 		<li> Fields serialization leaves a little more space for manoeuvre. 
-			If you do this then you may accept<br/> and return interfaces, e.g. List, Map; abstract classes etc, from your methods.
+			If you do this then you may accept<br/> and return interfaces, e.g. List, Map; abstract classes etc, from your methods
 		</li>
 		</ul>
 		<p>If you have the data on the server side, but nothing is coming through to the