Class and Description |
---|
ISolRSynchroniser
We don't use the Hibernate Listeners because we don't want to handle every
hibernate operations just a few one (we don't want to check if that class or
that one should be sync Synchronise the Gis Object with the full text search
engine.
|
Class and Description |
---|
GenericDao
A generic dao That implements basic functions with java 5.0 generics
|
GenericGisDao |
IAdmDao
Interface for
Adm data access |
IAlternateNameDao
Interface of data access object for
AlternateName |
ICityDao
Interface of data access object for
City |
ICountryDao
Interface of data access object for
Country |
IDao
Interface of a Generic (java-5 meaning) data access object
|
IDatabaseHelper
Interface that describe useful function to manage the database
|
IGisDao
Interface for a Generic Dao for GIS Object (java-5 meaning) it suppose that
the PK is of type long because its goal is to be used with class gisfeatures
and class that extends GisFeature. if it is note the case. it is possible to
create an other inteface
: public interface IGisDao |
IGisFeatureDao
Interface of data access object for
GisFeature |
IhouseNumberDao
Interface of data access object for
HouseNumber |
IIdGenerator
class to generate ids in order to add streets and place to the datastore and not be in conflict
|
IImporterStatusListDao |
ILanguageDao
Interface of data access object for
Language |
IOpenStreetMapDao |
IRepositoryStrategy |
ISolRSynchroniser
We don't use the Hibernate Listeners because we don't want to handle every
hibernate operations just a few one (we don't want to check if that class or
that one should be sync Synchronise the Gis Object with the full text search
engine.
|
IStatsUsageDao
Interface for
StatsUsage data access |
IZipCodeDao |
Class and Description |
---|
ICountryDao
Interface of data access object for
Country |
Class and Description |
---|
CitySubdivisionDao
A data access object for
CitySubdivision Object |
IAdmDao
Interface for
Adm data access |
IAlternateNameDao
Interface of data access object for
AlternateName |
ICityDao
Interface of data access object for
City |
ICountryDao
Interface of data access object for
Country |
IDatabaseHelper
Interface that describe useful function to manage the database
|
IGisDao
Interface for a Generic Dao for GIS Object (java-5 meaning) it suppose that
the PK is of type long because its goal is to be used with class gisfeatures
and class that extends GisFeature. if it is note the case. it is possible to
create an other inteface
: public interface IGisDao |
IGisFeatureDao
Interface of data access object for
GisFeature |
IhouseNumberDao
Interface of data access object for
HouseNumber |
IIdGenerator
class to generate ids in order to add streets and place to the datastore and not be in conflict
|
IImporterStatusListDao |
ILanguageDao
Interface of data access object for
Language |
IOpenStreetMapDao |
ISolRSynchroniser
We don't use the Hibernate Listeners because we don't want to handle every
hibernate operations just a few one (we don't want to check if that class or
that one should be sync Synchronise the Gis Object with the full text search
engine.
|
IZipCodeDao |
Class and Description |
---|
IOpenStreetMapDao |
Class and Description |
---|
CountryDao
A data access object for
Country |
IAlternateNameDao
Interface of data access object for
AlternateName |
ICityDao
Interface of data access object for
City |
ICountryDao
Interface of data access object for
Country |
IGisFeatureDao
Interface of data access object for
GisFeature |
IIdGenerator
class to generate ids in order to add streets and place to the datastore and not be in conflict
|
IOpenStreetMapDao |
ISolRSynchroniser
We don't use the Hibernate Listeners because we don't want to handle every
hibernate operations just a few one (we don't want to check if that class or
that one should be sync Synchronise the Gis Object with the full text search
engine.
|
IStatsUsageDao
Interface for
StatsUsage data access |
IZipCodeDao |
Copyright © 2015. All rights reserved.