Java Doc for ArcSDEDataStore.java in  » GIS » GeoTools-2.4.1 » org » geotools » arcsde » data » Java Source Code / Java DocumentationJava Source Code and Java Documentation

All remaining functionality is implemented against these methods, including Transaction and Locking Support. These implementations will not be optimal but they will work.

The common use case to create an ArcSDE layer is to setup the SeTable object with all the non-geometry attributes first, then create the SeLayer and set the geometry column name and its properties.

Will return null if there is not fast way to compute the bounds.

If getBounds(Query) returns -1 due to expense consider using getFeatures(Query).getCount() as a an alternative.

A subclass that supports the creation of such an optimized FeatureReader shold override this method.

Just for convenience, if the type name is not full qualified, it will be prepended by the "<DATABASE_NAME>.<USER_NAME>." string. Anyway, it is strongly recommended that you use only full qualified type names.

The common use case to create an ArcSDE layer is to setup the SeTable object with all the non-geometry attributes first, then create the SeLayer and set the geometry column name and its properties. This approach brings a nice problem, since we need to create the attributes in exactly the same order as specified in the passed FeatureType, which means that the geometry attribute needs not to be the last one.

To avoid this, the following workaround is performed: instead of creating the schema as described above, we will first create the SeTable with a single, temporary column, since it is not possible to create a table without columns. The, we will iterate over the AttributeTypes and add them as they appear using SeTable.addColumn(SeColumnDefinition). But if we found that the current AttributeType is geometric, instead of adding the column we just create the SeLayer object. This way, the geometric attribute is inserted at the end, and then we keep iterating and adding the rest of the columns. Finally, the first column is removed, since it was temporary (note that I advertise it, it is a _workaround_).

Sometimes some 'extra' information is required to correctly create the underlying ArcSDE SeLayer. For instance, a specific configuration keyword might be required to be used (instead of "DEFAULTS"), or a particular column might need to be marked as the rowid column for the featuretype. A non-null hints parameter contains a mapping from a list of well-known java.lang.String keys to values. The possible keys are listed in the table below. keys with any other values are ignored.

Parameters:
  featureType - the feature type containing the name, attributes andcoordinate reference system of the new ArcSDE layer.
Parameters:
  hints - A map containing extra ArcSDE-specific hints about how tocreate the underlying ArcSDE SeLayer and SeTable objects fromthis FeatureType.
throws:
  IOException - see throws DataSourceException bellow
throws:
  IllegalArgumentException - if the passed feature type does not contains at least onegeometric attribute, or if the type name contains '.' (dots).
throws:
  NullPointerException - if featureType is null
throws:
  DataSourceException - if there is not an available (free) connection to theArcSDE instance(in that case maybe you need to increase themaximun number of connections for the connection pool), or anSeException exception is catched while creating the featuretype at the ArcSDE instance (e.g. a table with that namealready exists).

key name	key value type	default value (if applicable)
configuration.keyword	java.lang.String	"DEFAULTS"
rowid.column.type	java.lang.String - "NONE", "USER" and "SDE" are the only valid values	"NONE"
rowid.column.name	java.lang.String	null