[MOBY-guts] biomoby commit

Martin Senger senger at pub.open-bio.org
Sun Aug 28 10:19:08 UTC 2005


senger
Sun Aug 28 06:19:08 EDT 2005
Update of /home/repository/moby/moby-live/Java/docs
In directory pub.open-bio.org:/tmp/cvs-serv5357/docs

Modified Files:
	Moses.html 
Added Files:
	Moses-generators.html Moses-parser.html 
Log Message:


moby-live/Java/docs Moses-generators.html,NONE,1.1 Moses-parser.html,NONE,1.1 Moses.html,1.3,1.4
===================================================================
RCS file: /home/repository/moby/moby-live/Java/docs/Moses.html,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- /home/repository/moby/moby-live/Java/docs/Moses.html	2005/08/27 21:38:03	1.3
+++ /home/repository/moby/moby-live/Java/docs/Moses.html	2005/08/28 10:19:08	1.4
@@ -38,6 +38,7 @@
 a String data type (with a predictable contents) (the code is
 available in jMoby): <p>
 
+<blockquote>
 <pre class=code>
 package org.jmoby.tutorial.service;
 
@@ -58,10 +59,12 @@
     }
 }
 </pre>
+</blockquote>
 <p>
 
 The service was registered in a Biomoby registry as follows: <p>
 
+<blockquote>
 <pre class=code>
 &lt;Services&gt;
   &lt;Service authURI='samples.jmoby.net'
@@ -89,6 +92,7 @@
   &lt;/Service&gt;
 &lt;/Services&gt;
 </pre>
+</blockquote>
 
 I have highlighted in both pictures a word <tt>greeting</tt>. It is an
 article name in a Biomoby registry, and it became a method name in a
@@ -98,6 +102,7 @@
 example (here it shows only part of the implementation class but its
 full version is in jMoby): <p>
 
+<blockquote>
 <pre class=code>
     /**************************************************************************
      * This is a mandatory method to be implemented.
@@ -124,6 +129,7 @@
 	    return new <b>simple_key_value_pair</b>[] {};
         ...
 </pre>
+</blockquote>
 <p>
 
 The <tt>Regex</tt> and <tt>simple_key_value_pair</tt> are Biomoby data
@@ -157,16 +163,20 @@
 their API documentation (note that you must have Internet connection
 because it explores Biomoby registry):
   
-  <pre>
-  ./build-dev.sh moses-datatypes
-  </pre>
+<blockquote>
+<pre class=script>
+./build-dev.sh moses-datatypes
+</pre>
+</blockquote>
 
   <li class=count> <b>Generate skeleton for your service</b>, compile
 it, generate its API:
 
-  <pre>
-  ./build-dev.sh -Dmoses.service=TheService moses-services
-  </pre>
+<blockquote>
+<pre class=script>
+./build-dev.sh -Dmoses.service=TheService moses-services
+</pre>
+</blockquote>
 
   <li class=count> <b>Write your own implementation</b>, for example a
 class <tt>TheServiceImpl</tt>, that extends skeleton
@@ -176,17 +186,21 @@
 Tomcat). If you place your source code into <tt>src/samples</tt> - use
 whatever package you like - you can compile it using jMoby Ant:
 
-  <pre>
-  ./build-dev.sh
-  </pre>
+<blockquote>
+<pre class=script>
+./build-dev.sh
+</pre>
+</blockquote>
 
   <li class=count> Start your Tomcat and <b>deploy your
 implementation</b> to your Tomcat (<em>sorry, this is not yet fully
 implemented</em>):
 
-  <pre>
-  ./build-dev.sh -Dservice.name=TheService deploy-services
-  </pre>
+<blockquote>
+<pre class=script>
+./build-dev.sh -Dservice.name=TheService deploy-services
+</pre>
+</blockquote>
   
 </ol>
        
@@ -222,7 +236,7 @@
 neighbourhood (other services that can be connected with this
 one). Here is an example extract from service API: <p>
 
-<a href="images/service-api-example.png"><img src="images/service-api-example-small.png" border=0></a>       
+<a href="images/service-api-example.png"><img src="images/service-api-example-small.jpg" border=0></a>       
 
   <li> It has built-in access to the deployment parameters (the
 parameters that can give service necessary configuration properties,
@@ -253,9 +267,36 @@
 <a name="components"></a>
 <h2>MoSeS Components</h2>
 
+The documents listed below explain in details the whole Moses
+project. Because the main purpose of Moses is to support service
+providers, sometimes documentation focuses more on development ("how
+to write a code", "how it is done") rather on a randomly walking-in
+end-users ("how to use it"). If you are the latter you may find most
+in the sections describing various supporting command-line
+clients. <p>
 
 
+The Moses consists of four major parts: <p>
+
+<ul>
+   <li> <a href="Moses-generators.html">Code Generators</a>
+	<ul>
+	  <li class=tiny> <a href="Moses-generators.html#datatypes">Data types generator</a>
+	  <li class=tiny> <a href="Moses-generators.html#skeletons">Service skeletons generator</a>
+	</ul>
+	<p>
+
+   <li> <a href="Moses-parser.html">Biomoby XML Parser</a> and
+associated general data types for storage <p>
 
+   <li> Support on the client side (<em>not yet documented</em>), and
+
+   <li> Support for service deployment (<em>not yet fully implemented</em>)
+
+</ul><p>
+
+
+<hr>
 <p>
 
 Documentation in progress... <img src="images/arbeiter.gif" border=0/> (as long as I can keep my eyes open): <p>
@@ -264,17 +305,13 @@
 
 Will be (almost) finished before the end of August 2005... <p>
 
-Look here: <a
-href="http://www.ebi.ac.uk/~senger/jMoby/APIservices/index.html"
-target="_top">API of generated data types and services</a>.
-
 <p>
 
 <hr>
 <div align=right class="address">
 <address><A HREF="mailto:martin.senger at gmail.com">Martin Senger</A><BR></address>
 <!-- hhmts start -->
-Last modified: Sun Aug 28 06:32:31 2005
+Last modified: Sun Aug 28 19:03:43 2005
 <!-- hhmts end -->
 </div>
 




More information about the MOBY-guts mailing list