Recent Development (as of August 2008)

For the 2.2.x branch the arcsde module has returned to the build process with a stub jar to replace ESRI dependencies.

For the 2.3.x branch, there is an initial implementation of ArcSDE Raster Support.  You can find out about it here.

For the 2.4.x branch arcsde is working on returning to supported status; we need to provide a profile for nightly builds to run. ArcSDE Raster Support is also available on 2.4.x as well. You can find out about it at the ArcSDE Raster Support page.

For the 2.5.x branch arcsde has been almost completely rewritten, it no longer extends AbstractDatatore and the code is much easier to follow. Internally it protects all SeConnection use behind a Queue (rather than a Lock) as a way of addressing concurrent usage in a fair manner.

Also, it has been extended to support the read and edition of versioned tables, limited to edit the default version.

IP Review

Please refer to:

• http://svn.geotools.org/geotools/trunk/gt/modules/unsupported/arcsde/review.txt

Outstanding Issues

jira.codehaus.org (20 issues)
T	Key	Summary	Assignee	Reporter	Pr	Status	Res	Created	Updated	Due
	GEOT-423	createSchema needs the CRS's valid coordinate range	Gabriel Roldán	Gabriel Roldán		Open	UNRESOLVED	Feb 14, 2005	Nov 15, 2006
	GEOT-1705	Or'ed spatial filters are being and'ed instead	Gabriel Roldán	Gabriel Roldán		Open	UNRESOLVED	Feb 12, 2008	Sep 23, 2008
	GEOT-1956	If there are a lot of layers in an ArcSDE database performance degrades unacceptably	Gabriel Roldán	Gabriel Roldán		Open	UNRESOLVED	Aug 21, 2008	Sep 23, 2008
	GEOT-1213	Fid filter can geneate unsupported SQL on Oracle	Saul Farber	Shaun Forbes		Reopened	UNRESOLVED	Mar 29, 2007	Jun 05, 2007
	GEOT-1633	FilterToSQLSDE broken on FilterCapabilities class cast exception	Gabriel Roldán	Jody Garnett		Open	UNRESOLVED	Dec 18, 2007	Dec 20, 2007
	GEOT-1194	Polygon with holes not handled by	Gabriel Roldán	Lars Aksel Opsahl		Open	UNRESOLVED	Mar 09, 2007	Mar 16, 2008
	GEOT-1776	versioned edit tests fail to run against ArcSDE 9.2	Gabriel Roldán	Saul Farber		Open	UNRESOLVED	Apr 18, 2008	Apr 18, 2008
	GEOT-1944	Difference between FeatureBounds and FeatureCollectionBounds	Gabriel Roldán	Jody Garnett		Open	UNRESOLVED	Aug 06, 2008	Aug 06, 2008
	GEOT-1750	Support ArcSDE Rasters with no colormap and pixel type SeRaster.SE_PIXEL_TYPE_32BIT_REAL (floating point rasters)	Saul Farber	Saul Farber		Open	UNRESOLVED	Mar 20, 2008	Sep 04, 2008
	GEOT-1744	Support ArcSDE Raster Catalogs made up of any supported raster storage type	Saul Farber	Saul Farber		Open	UNRESOLVED	Mar 18, 2008	Sep 04, 2008
	GEOT-1743	Support ArcSDE Rasters with colormap and pixel type SeRaster.SE_PIXEL_TYPE_8BIT_U	Saul Farber	Saul Farber		Open	UNRESOLVED	Mar 18, 2008	Sep 04, 2008
	GEOT-1728	ArcSdeDataStoreFactory.determineJsdeVersion missbehaves whith 9.2 database and 9.1 jars	Saul Farber	Gabriel Roldán		Open	UNRESOLVED	Mar 14, 2008	Sep 04, 2008
	GEOT-1394	ArcSDE query.getCount() sometimes returns inaccurate result	Saul Farber	Tyler Erickson		Open	UNRESOLVED	Jul 15, 2007	Sep 04, 2008
	GEOT-1387	Clean up ArcSDE module so that it gets more "stars"	Saul Farber	Saul Farber		Open	UNRESOLVED	Jul 11, 2007	Sep 04, 2008
	GEOT-362	TransactionInsert not working through Geoserver	Gabriel Roldán	Cougar Jay		Open	UNRESOLVED	Dec 25, 2004	Sep 04, 2008
	GEOT-2024	ArcSDE NStrings	Gabriel Roldán	Jared Erickson		Open	UNRESOLVED	Sep 09, 2008	Sep 09, 2008
	GEOT-1943	Simplify filters before issuing SDE requests	Gabriel Roldán	Andrea Aime		In Progress	UNRESOLVED	Aug 05, 2008	Sep 23, 2008
	GEOT-1421	WFS Query with spatial operator Equals and a line geometry does not work against SDE (version 9.1)	Saul Farber	Aleda Freeman		Open	UNRESOLVED	Aug 03, 2007	Aug 16, 2007
	GEOT-1684	Support ArcSDE domains in the ArcSDE plugin	Saul Farber	Saul Farber		Open	UNRESOLVED	Jan 22, 2008	Jan 22, 2008
	GEOT-1878	plugin/arcsde test-data needs to be documented.	Saul Farber	Adrian Custer		Open	UNRESOLVED	Jul 04, 2008	Jul 10, 2008

Getting ArcSDE to 'supported' status

There are five 'support stars' to earn. In order to get the ArcSDE module to supported status, we need at least four, and eventually five.

status	description
	Passes IP check, basically has correct headers
	Releasable - has no non blocking bugs in jira
	Used in anger - Used by GeoServer or uDig on large real world datasets – used by MassGIS to serve the statewide landuse dataset. Takes 15 minutes to grind through the renderer, but it works!
	Optimized - has been tuned to meet hard performance requirements (example shapefile)
	Supported - user docs, module maintainer watches user list, answers email etc.. – Both Gabriel Roldán and Saul Farber watch the list. Javadocs could use a review.

The current DataStore is not stable when

Design and Research Pages

Building a Working ArcSDE using the jsde jars

To connect to ArcSDE from java code, ESRI publishes a java library which is split across 2, 3 or 4 jars (depending on the version you use). These "java-to-ArcSDE connector jars" are here called the 'jsde' jars, so as to seperate them from our own ArcSDE module.

The ArcSDE module relies on the jsde jars for all its direct communication to ArcSDE, as indeed any java-based ArcSDE client application does. However, due to concerns about redistributing ESRI's jsde jars, geotools wanted to avoid having everyone who built gt2 download the jsde jars from the geotools maven site. This was accomplished by the use of a 'dummy' api, which is an exact mimic of the jsde api, only it doesn't actually do anything. It's simply classes which allow compilation of the ArcSDE module, without actually having or downloading the jsde jar files.

If you want to actually connect to ArcSDE using the ArcSDE module, you'll need to download the jsde jars and instruct maven to actually use them when building the ArcSDE module.

You have to build your module against the jsde jars if you want to use it to really access ArcSDE There have been reports of problems if you: 1. Build the ArcSDE module against the dummy api 2. Copy the ArcSDE module into their application, leaving the dummy api behind 3. Copy the actual jsde jars into their application 4. Run the dummy-built module against the real jsde jars and try to access ArcSDE and fetch data Mostly these problems have to do with static final constants which have different values and get inlined by the compiler. There is a jira issue to track this, so if you need to do the above, check it out

The jsde jars are actually very easily available. You can download the 9.1 jars here Just unroll the tar, zip and then tar files that you get, and extract the jsde_sdk.jar and jsde_pde.jar files.

Here's how to build the ArcSDE module with the real jsde jars:

$ mvn -DhaveSDEJars=
true -Dmaven.test.skip clean
install
        

$ mvn -DhaveSDEJars=
true -Dsde.version=9.2
-Dmaven.test.skip clean install