The Java Binding

The Java binding maps the EYEDB object model into Java by introducing a generic API and a tool to generate a speficic Java API from a given schema, built upon the generic API.

The generic Java API is made up of about one hundred and fifty classes such as some abstract classes as the object and class classes and some more concrete classes such as the database and image classes.

Each type in the EYEDB object model is implemented as a Java class whithin the Java API: there is a one for one mapping between the object model and the Java API.
This mapping follows a very simple naming schema: each Java class mapped from a type has the name of this type prefixed by org.eyedb..
For instance, the object type in the EYEDB object model is mapped on the org.eyedb.Object Java class, while the agregat is mapped to the org.eyedb.Agregat Java class.

The use of the Java language for an EYEDB binding has been motivated by several reasons:

• Java is architecture independent.
• Java is indeed valuable for distributed network environment.
• Java has a very rich builtin library.
• Java is secure.
• Java is easier to program than C++.

The Java binding is very close from the C++ binding: the class interfaces are identical, the functionalities are the same; only the language is slightly different.