|
Version: 1.1.1 | |||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
MobyObject
and all Biomoby primitive
types).
See:
Description
Interface Summary | |
---|---|
MapDataTypesIfc |
Class Summary | |
---|---|
MapPrimitiveDataTypes | Class containing static mapping between Biomoby primitive data types and names of classes they are represented by. |
MobyBoolean | An object representing a Boolean, a Moby primitive data type. |
MobyDateTime | An object representing a date, or a date and time, a Moby primitive data type. |
MobyFloat | An object representing a Float, a Moby primitive data type. |
MobyInteger | An object representing an Integer, a Moby primitive data type. |
MobyObject | An object representing a Biomoby Object, the main Biomoby data type, where all other data types are inherited from. |
MobyString | An object representing a String, a Moby primitive data type. |
MobyXref | An object representing a cross reference. |
The package org.biomoby.shared.datatypes contains containers
for basic Biomoby data types (a basic parent class MobyObject
and all Biomoby primitive
types).
However, you can find here (usually) much more classes: actually classes for all Biomoby data types as they appear in a Biomoby registry. These classes were (or could be, if you do not see them) generated automatically.
The instances of the classes located here are used for carrying real
data from a Biomoby clients to the Biomoby services, and
vice-versa. This makes them different from (some of) the classes
located in the org.biomoby.shared
package where are classes
used to communicate with a Biomoby registry.
Note that similar containers (aimed also to carry
real data from clients to Biomoby services, back and forth) are
located in the org.biomoby.shared.data
package. We simple
have more ways to do the same things.
The main use of the objects located here is together with the
automatically generated other Biomoby objects (they are generated from
the information stored in the Biomoby registry - in its data type
ontology section). Usually, these objects are created by a MobyParser
instance, and they all together
constitute the main object representing a full Biomoby input or output
- an instance of a MobyPackage
class. The way how to generate additional data types and how to use
them in order to get a comprehensive support for Biomoby service
providers see documentation for the MoSeS - Moby Services Support (if
this link does not work, try this
one).
An exception is the class MapPrimitiveDataTypes
and its
(generated) subclass MapDataTypes. These classes contain
mapping between the Biomoby data type names and the names of the Java
classes they are represented in.
|
Version: 1.1.1 | |||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |