\r
<h3><a name="jabaclient" id="jabaclient"></a>What is JABAWS client?</h3>\r
<p>\r
- A JABAWS client is a program that lets you run the bioinformatics methods for which a JABAWS server provides web \r
- services. The most basic JABAWS client is a command line Java application which can call any of the JABAWS web \r
- services methods on any instance of JABAWS Server that it can reach over the web. It is useful if you want to \r
- test, or execute the programs provided by a JABAWS server in your own scripts, and do not want to handle any web \r
- service specific details. The client is open source, so you can also use its source code to find out how to work \r
- with JABA Web Services if you would like to write your own client software. \r
- <a href="http://www.jalview.org/">Jalview</a>, which is a multiple sequence alignment and analysis application, \r
- provides a graphical JABAWS client. This client has the same functionality as the command line client, but \r
- instead allows JABAWS services to be accessed in a more user-friendly manner, through a graphical user interface.\r
+ A JABAWS client is a Java application that lets you run the programs for which a JABAWS server provides web \r
+ services. The most basic JABAWS client is a command line application this is able to call any of the JABAWS web \r
+ services on any instance of JABAWS Server available over the web. The basic client is useful if you would like \r
+ to test or execute the programs provided by theJABAWS server in your own scripts, but you do not want to handle \r
+ any web service specific details. The client is an open source software, so you can also use the source code to \r
+ as an example how to manipulate with JABAWS web services in your own code. \r
+ <a href="http://www.jalview.org/">Jalview</a>, a multiple sequence alignment and analysis application, is a good \r
+ example of a graphical JABAWS client. This client uses the same functionality as the command line client, but \r
+ instead allows JABAWS services to be accessed in a more user-friendly manner, through a graphical user interface.\r
</p>\r
\r
\r
\r
<h3><a name="jalviewsup"></a>JABAWS versions compatibility and Jalview support </h3>\r
<p>\r
- JABAWS version 2.1 is fully backward compatible with JABAWS v1.0 and v2.0. That means that all JABAWS v1.0 and \r
- v2.0 clients should also be able to use JABAWS 2.1 services. To access the analysis web services introduced in\r
- JABAWS 2.0, however, clients that were designed for JABAWS v1.0 must be updated.\r
+ JABAWS version 2.1 is fully backward compatible with JABAWS v1.0 and v2.0. This means all JABAWS 1.0 and 2.0 and \r
+ 2.0.1 clients should also be able to use JABAWS 2.1 services. To access the analysis web services introduced in \r
+ JABAWS 2.0, however, clients that were designed for JABAWS v1.0 must be updated.\r
</p>\r
\r
\r
\r
<h3><a name="cmdclient" id="cmdclient"></a>Programmatic access to JABAWS </h3>\r
<p>\r
- JABA Web Services are WS-I basic profile compliant, which means they can be accessed using any programming language \r
+ JABAWS web services are WS-I basic profile compliant, which means they can be accessed using any programming language \r
or system that can utilize standard SOAP web services. The WSDL for each service is published on the JABAWS home \r
- page, and you can use this to automatically generate service bindings for your program. If you use Java, however, \r
- then you may wish to use our <a href="http://www.compbio.dundee.ac.uk/download">client package</a> to access JABAWS. \r
+ page, and you can use this to automatically generate service bindings for your program. If you use Java \r
+ you may wish to use our <a href="http://www.compbio.dundee.ac.uk/download">client package</a> to access JABAWS. \r
This package is based on the autogenerated source code produced by <span class="hightlight">wsimport</span>, which \r
is the Java tool for creating web service bindings; but in addition, offers some additional methods which simplify \r
working with JABAWS. For more information please refer to the <a href="dm_javadoc/index.html">data model javadoc</a>.\r
<h4><a name="projstruct" id="projstruct"></a>Structure of the project</h4>\r
<ul>\r
<li><span class="directory">binaries</span> contains native executables e.g. clustalw</li>\r
- <ul>\r
- <li><span class="directory">src</span> contains sources of native executables</li>\r
- <li><span class="directory">windows</span> contains pre-compiled Windows binaries</li>\r
- <li>compilebin.sh - the script to complile binaries</li>\r
- <li>setexecflag.sh - the script to set executable flag for the binaries</li>\r
- </ul>\r
+ <li style="list-style-position:inside"><span class="directory">src</span> contains sources of native executables</li>\r
+ <li style="list-style-position:inside"><span class="directory">windows</span> contains pre-compiled Windows binaries</li>\r
+ <li style="list-style-position:inside">compilebin.sh - the script to complile binaries</li>\r
+ <li style="list-style-position:inside">setexecflag.sh - the script to set executable flag for the binaries</li>\r
<li><span class="directory">conf</span> contains JABAWS configuration files </li>\r
<li><span class="directory">ExecutionStatistics</span> the database for storing collected execution statistics </li>\r
<li><span class="directory">jobsout</span> a default folder for temporary job directories </li>\r
<li><span class="directory">statpages</span> the web pages for execution statistics display</li>\r
<li><span class="directory">WEB-INF</span> default </li>\r
<li><span class="directory">website</span> contains the JABAWS web pages </li>\r
- <ul>\r
- <li><span class="directory">archive</span> contains JABAWS packages, the WAR and JAR files</li>\r
- </ul>\r
+ <li style="list-style-position:inside"><span class="directory">archive</span> contains JABAWS packages, the WAR and JAR files</li>\r
+\r
</ul>\r
<h4><a name="thecode" id="thecode"></a>The code structure</h4>\r
<ul>\r