GeoServer

Aliasing "broken" in WFS1.1 DFT

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.6.3
  • Fix Version/s: 1.6.5
  • Component/s: WFS
  • Labels:
    None
  • Number of attachments :
    0

Description

The alias implementation we sponsored was mainly centered around WFS1.0 ... due to ArcGIS not sending a version with its WFS requests (see #1931), the returned WFS1.1 response is causing us significant headaches due to the following ...

1. Getcapabilities

/wfs?SERVICE=WFS&REQUEST=getcapabilities

<FeatureType>
<Name>slip:LGATE-001</Name>

2. ArcGIS will then do a DFT on the given featuretype

/wfs?SERVICE=WFS&VERSION=1.1.0&REQUEST=describefeaturetype&typename=slip:LGATE-001

3. Geoserver returns the followin element ...

<xsd:element name="lgate_001" substitutionGroup="gml:_Feature" type="slip:LGATE-001Type"/>

Note the name value is actually the table name and not the alias.

4. ArcGIS then attempts to GetFeature on lgate_001 which obviously will fail

wfs?SERVICE=WFS&VERSION=1.1.0&REQUEST=getfeautre&typename=lgate_001....

Could not find type: {http://www.openplans.org/topp}lgate_001

WFS1.0 is without problems.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Andrea Aime added a comment -

I see... as a temporary workaround can you hit the GetCapabilities request with /wfs?SERVICE=WFS&REQUEST=getcapabilities&version=1.0.0?

Show
Andrea Aime added a comment - I see... as a temporary workaround can you hit the GetCapabilities request with /wfs?SERVICE=WFS&REQUEST=getcapabilities&version=1.0.0?
Hide
Permalink
Andrea Aime added a comment -

Or else, more than a workaround that's the proper way to ask for the WFS 1.0 capabilities anyways. The bug in wfs 1.1 DFT stands

Show
Andrea Aime added a comment - Or else, more than a workaround that's the proper way to ask for the WFS 1.0 capabilities anyways. The bug in wfs 1.1 DFT stands
Hide
Permalink
Chris Tweedie added a comment -

Completely agree that the root cause lies in ArcGIS Andrea however supporting this major client is pretty paramount for us at least.

Anyone using GS1.6.x WFS with aliased table names will not be able to support any version of ArcGIS up to 9.3Beta (i am pretty sure 9.3 passes the version now). If we can fix this, there probably no reason to keep 1931 open

Show
Chris Tweedie added a comment - Completely agree that the root cause lies in ArcGIS Andrea however supporting this major client is pretty paramount for us at least. Anyone using GS1.6.x WFS with aliased table names will not be able to support any version of ArcGIS up to 9.3Beta (i am pretty sure 9.3 passes the version now). If we can fix this, there probably no reason to keep 1931 open
Hide
Permalink
Andrea Aime added a comment -

Fixed in 1.6.x and trunk. Chris, you can try this out by grabbing a nightly >= 27 may from http://gridlock.openplans.org/geoserver/1.6.x/

Show
Andrea Aime added a comment - Fixed in 1.6.x and trunk. Chris, you can try this out by grabbing a nightly >= 27 may from http://gridlock.openplans.org/geoserver/1.6.x/

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.