[Geoserver-users] PostgreSQL arrays and enumerations vs. WFS?

GeoServer GeoServer User
1

Hello, GeoServer-ers,

I just hooked up a PostGIS (8.3.5-1/1.3.4-1) database to GeoServer (1.7.1a) (in Tomcat 6.0.18) and created a new FeatureType from a table therein. Everything is perfectly fine, except for the absence of two fields in the table in the GeoServer FeatureType config and their uniform absence in GML features returned to GetFeature (all outputformat versions of GML). The datatype of one is an array of integers, and that of the other an array of an enumeration. Trying to switch to a custom schema from the config page throws a:

FeatureType Editor problem:javax.servlet.jsp.JspException: Getter for property attributeNames threw exception: java.lang.ClassCastException: org.vfny.geoserver.form.data.AttributeForm

Is there an expected behavior for those types of fields? Is this it?

Is this really a GeoTools question?

I'm prepared to investigate with traces, but if there's a simple answer, that would naturally be preferable.

Thanks!

---
A. Soroka / Digital Scholarship Services R & D
the University of Virginia Library

2

ajs6f ha scritto:

Hello, GeoServer-ers,

I just hooked up a PostGIS (8.3.5-1/1.3.4-1) database to GeoServer (1.7.1a) (in Tomcat 6.0.18) and created a new FeatureType from a table therein. Everything is perfectly fine, except for the absence of two fields in the table in the GeoServer FeatureType config and their uniform absence in GML features returned to GetFeature (all outputformat versions of GML). The datatype of one is an array of integers, and that of the other an array of an enumeration. Trying to switch to a custom schema from the config page throws a:

FeatureType Editor problem:javax.servlet.jsp.JspException: Getter for property attributeNames threw exception: java.lang.ClassCastException: org.vfny.geoserver.form.data.AttributeForm

Is there an expected behavior for those types of fields? Is this it?

Is this really a GeoTools question?

I'm prepared to investigate with traces, but if there's a simple answer, that would naturally be preferable.

What you have there is a complex feature, array attributes have
maxOccur > 1 and... complex features are not supported neither
by GeoTools nor by GeoServer.

Justin can probably fill in with more details xml wise.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.

3

What you have there is a complex feature, array attributes have
maxOccur > 1 and... complex features are not supported neither
by GeoTools nor by GeoServer.

Justin can probably fill in with more details xml wise.

Yeah... you are sort of out of luck as Andrea says, arrays of attributes are not really supported. Although it would be nice if GeoServer did not cough up an exception and just treated it like a generic object.

Can you provide the full stack trace? We might be able to find a work around.

-Justin

Cheers
Andrea

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.