GeoServer

GML featureTypeCache does not qualify entries by namespace

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Cannot Reproduce
  • Affects Version/s: 1.6.4, 1.7.0-RC1
  • Fix Version/s: 1.7.5
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

If you have two feature types in different namespaces a WFS GetFeature will bomb out because it tries to seed the cache with both feature types but does not qualify them by namespace.

Activity

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

I've tried setting up three layers with the same name:

  • topp:states (usual shapefile)
  • cite:states (same shapefile as above, different namespace)
  • sde:states (shapefile exported to postgis, one column removed to make sure the feature type was not the same)

Then I tried hitting GeoServer with GetFeatureType, DescribeFeatureType, GetFeature and Transaction (update in particular).
None of them seems to fail, haven't noticed any of these problems. Maybe the cache has already been fixed in 1.7.x?

Here is a few of the request I made:

<!-- Performs a get feature with a bounding box filter.      -->
<!-- The BBOX filter is a convenience for a <Not><Disjoint>, -->
<!-- it fetches all features that spatially interact with the given box. -->
<!-- This example also shows how to request specific properties, in this -->
<!-- case we just get the STATE_NAME and PERSONS -->

<wfs:GetFeature service="WFS" version="1.0.0"
  outputFormat="GML2"
  xmlns:cite="http://www.opengeospatial.net/cite"
  xmlns:wfs="http://www.opengis.net/wfs"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:gml="http://www.opengis.net/gml"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wfs
                      http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd">
  <wfs:Query typeName="cite:states">
    <ogc:PropertyName>topp:STATE_NAME</ogc:PropertyName>
    <ogc:PropertyName>topp:PERSONS</ogc:PropertyName>
    <ogc:Filter>
      <ogc:BBOX>
        <ogc:PropertyName>the_geom</ogc:PropertyName>
        <gml:Box srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
           <gml:coordinates>-75.102613,40.212597 -72.361859,41.512517</gml:coordinates>
        </gml:Box>
      </ogc:BBOX>
   </ogc:Filter>
  </wfs:Query>
</wfs:GetFeature>

<!-- Performs a get feature with a bounding box filter.      -->
<!-- The BBOX filter is a convenience for a <Not><Disjoint>, -->
<!-- it fetches all features that spatially interact with the given box. -->
<!-- This example also shows how to request specific properties, in this -->
<!-- case we just get the STATE_NAME and PERSONS -->

<wfs:GetFeature service="WFS" version="1.1.0"
  xmlns:cite="http://www.opengeospatial.net/cite"
  xmlns:wfs="http://www.opengis.net/wfs"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:gml="http://www.opengis.net/gml"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wfs
                      http://schemas.opengis.net/wfs/1.1.0/wfs.xsd">
  <wfs:Query typeName="cite:states">
    <wfs:PropertyName>topp:STATE_NAME</wfs:PropertyName>
    <wfs:PropertyName>topp:PERSONS</wfs:PropertyName>
    <ogc:Filter>
      <ogc:BBOX>
        <ogc:PropertyName>the_geom</ogc:PropertyName>
        <gml:Envelope srsName="http://www.opengis.net/gml/srs/epsg.xml#4326">
           <gml:lowerCorner>-75.102613 40.212597</gml:lowerCorner>
           <gml:upperCorner>-72.361859 41.512517</gml:upperCorner>
        </gml:Envelope>
      </ogc:BBOX>
   </ogc:Filter>
  </wfs:Query>
</wfs:GetFeature>

http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=cite:states&propertyName=STATE_NAME,PERSONS&maxFeatures=1
http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=topp:states&propertyName=STATE_NAME,PERSONS&maxFeatures=1

<wfs:Transaction service="WFS" version="1.0.0"
  xmlns:topp="http://www.openplans.org/topp"
  xmlns:ogc="http://www.opengis.net/ogc"
  xmlns:wfs="http://www.opengis.net/wfs">
  <wfs:Update typeName="cite:states">
    <wfs:Property>
      <wfs:Name>PERSONS</wfs:Name>
      <wfs:Value>50</wfs:Value>
    </wfs:Property>
    <ogc:Filter>
      <ogc:FeatureId fid="states.1"/>
    </ogc:Filter>
  </wfs:Update>
</wfs:Transaction>


<DescribeFeatureType
  version="1.0.0"
  service="WFS"
  xmlns="http://www.opengis.net/wfs"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd">
  
    <TypeName>sde:states</TypeName>
    
</DescribeFeatureType>
Show
Andrea Aime added a comment - I've tried setting up three layers with the same name: topp:states (usual shapefile) cite:states (same shapefile as above, different namespace) sde:states (shapefile exported to postgis, one column removed to make sure the feature type was not the same) Then I tried hitting GeoServer with GetFeatureType, DescribeFeatureType, GetFeature and Transaction (update in particular). None of them seems to fail, haven't noticed any of these problems. Maybe the cache has already been fixed in 1.7.x? Here is a few of the request I made: <!-- Performs a get feature with a bounding box filter. --> <!-- The BBOX filter is a convenience for a <Not> <Disjoint> , --> <!-- it fetches all features that spatially interact with the given box. --> <!-- This example also shows how to request specific properties, in this --> <!-- case we just get the STATE_NAME and PERSONS --> <wfs:GetFeature service= "WFS" version= "1.0.0" outputFormat= "GML2" xmlns:cite = "http://www.opengeospatial.net/cite" xmlns:wfs = "http://www.opengis.net/wfs" xmlns:ogc = "http://www.opengis.net/ogc" xmlns:gml = "http://www.opengis.net/gml" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd"> <wfs:Query typeName= "cite:states" > <ogc:PropertyName> topp:STATE_NAME </ogc:PropertyName> <ogc:PropertyName> topp:PERSONS </ogc:PropertyName> <ogc:Filter> <ogc:BBOX> <ogc:PropertyName> the_geom </ogc:PropertyName> <gml:Box srsName= "http://www.opengis.net/gml/srs/epsg.xml#4326" > <gml:coordinates> -75.102613,40.212597 -72.361859,41.512517 </gml:coordinates> </gml:Box> </ogc:BBOX> </ogc:Filter> </wfs:Query> </wfs:GetFeature> <!-- Performs a get feature with a bounding box filter. --> <!-- The BBOX filter is a convenience for a <Not> <Disjoint> , --> <!-- it fetches all features that spatially interact with the given box. --> <!-- This example also shows how to request specific properties, in this --> <!-- case we just get the STATE_NAME and PERSONS --> <wfs:GetFeature service= "WFS" version= "1.1.0" xmlns:cite = "http://www.opengeospatial.net/cite" xmlns:wfs = "http://www.opengis.net/wfs" xmlns:ogc = "http://www.opengis.net/ogc" xmlns:gml = "http://www.opengis.net/gml" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.1.0/wfs.xsd"> <wfs:Query typeName= "cite:states" > <wfs:PropertyName> topp:STATE_NAME </wfs:PropertyName> <wfs:PropertyName> topp:PERSONS </wfs:PropertyName> <ogc:Filter> <ogc:BBOX> <ogc:PropertyName> the_geom </ogc:PropertyName> <gml:Envelope srsName= "http://www.opengis.net/gml/srs/epsg.xml#4326" > <gml:lowerCorner> -75.102613 40.212597 </gml:lowerCorner> <gml:upperCorner> -72.361859 41.512517 </gml:upperCorner> </gml:Envelope> </ogc:BBOX> </ogc:Filter> </wfs:Query> </wfs:GetFeature> http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=cite:states&propertyName=STATE_NAME,PERSONS&maxFeatures=1 http://localhost:8080/geoserver/wfs?request=GetFeature&version=1.1.0&typeName=topp:states&propertyName=STATE_NAME,PERSONS&maxFeatures=1 <wfs:Transaction service= "WFS" version= "1.0.0" xmlns:topp = "http://www.openplans.org/topp" xmlns:ogc = "http://www.opengis.net/ogc" xmlns:wfs = "http://www.opengis.net/wfs" > <wfs:Update typeName= "cite:states" > <wfs:Property> <wfs:Name> PERSONS </wfs:Name> <wfs:Value> 50 </wfs:Value> </wfs:Property> <ogc:Filter> <ogc:FeatureId fid= "states.1" /> </ogc:Filter> </wfs:Update> </wfs:Transaction> <DescribeFeatureType version= "1.0.0" service= "WFS" xmlns= "http://www.opengis.net/wfs" xmlns:xsi = "http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation= "http://www.opengis.net/wfs http://schemas.opengis.net/wfs/1.0.0/WFS-basic.xsd" > <TypeName> sde:states </TypeName> </DescribeFeatureType>
Hide
Permalink
Justin Deoliveira added a comment -

Interesting... i wonder if this is a problem with caching... The user defines a feature type in a namespace, does some requests, changes it, adds a new one... does more requests... not sure.

But yeah... perhaps it is fixed on 1.7.x due to the feature model switch over... I will ask the original reporter for more info.

Show
Justin Deoliveira added a comment - Interesting... i wonder if this is a problem with caching... The user defines a feature type in a namespace, does some requests, changes it, adds a new one... does more requests... not sure. But yeah... perhaps it is fixed on 1.7.x due to the feature model switch over... I will ask the original reporter for more info.
Hide
Permalink
A. Soroka added a comment -

I'm the original reporter Mr. Deoliveria mentions. I can add the following information:

I just tried the same config setup (data directory) with 1.7RC1, only to find the exact same behavior. So something perhaps more subtle is at work?

My config relies on PostGIS for every datastore (well over a thousand now in a few dozen different namespaces). I'll try loading up some shapefiles to see if that makes any difference.

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

Show
A. Soroka added a comment - I'm the original reporter Mr. Deoliveria mentions. I can add the following information: I just tried the same config setup (data directory) with 1.7RC1, only to find the exact same behavior. So something perhaps more subtle is at work? My config relies on PostGIS for every datastore (well over a thousand now in a few dozen different namespaces). I'll try loading up some shapefiles to see if that makes any difference. — A. Soroka / Digital Scholarship Services R & D the University of Virginia Library
Hide
Permalink
A. Soroka added a comment -

I forgot to add something that may be quite important: the error I'm producing is not dependent on there being multiple featureTypes in different namespaces with the same "local name". It occurs for every featureType.

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

Show
A. Soroka added a comment - I forgot to add something that may be quite important: the error I'm producing is not dependent on there being multiple featureTypes in different namespaces with the same "local name". It occurs for every featureType. — A. Soroka / Digital Scholarship Services R & D the University of Virginia Library
Hide
Permalink
Andrea Aime added a comment -

What do you mean it happens for every feature type? Can you still reproduce the issue? If so, can you provide
steps to do so from a clean configuration?

Show
Andrea Aime added a comment - What do you mean it happens for every feature type? Can you still reproduce the issue? If so, can you provide steps to do so from a clean configuration?
Hide
Permalink
A. Soroka added a comment -

By 'every', I mean that it doesn't matter what feature type for which you ask-- the error is independent of that parameter.

I'm afraid I don't have the time or resources to set up a clean install to reproduce the problem, primarily because I'm handing off our project to another programmer. I'll bring her up to speed on this issue and hopefully she'll be able to help further.

Show
A. Soroka added a comment - By 'every', I mean that it doesn't matter what feature type for which you ask-- the error is independent of that parameter. I'm afraid I don't have the time or resources to set up a clean install to reproduce the problem, primarily because I'm handing off our project to another programmer. I'll bring her up to speed on this issue and hopefully she'll be able to help further.
Hide
Permalink
Justin Deoliveira added a comment -

I am going to close this one for now. Please re-open with instructions of how to reproduce and we will be happy to solve it.

Show
Justin Deoliveira added a comment - I am going to close this one for now. Please re-open with instructions of how to reproduce and we will be happy to solve it.
Hide
Permalink
Miles Jordan added a comment -

This is a funny one. I had this problem just now with version 2.0.

I had two different layers with the same name but different namespaces. GetFeature would return this error using WFS 1.1.0 but was ok with version 1.0.0.

I removed one of the layers and it started working. But then I tried to put it back to reproduce the problem and I couldn't reproduce it either!

If I see it come up again I'll try a bit more to reproduce it.

Show
Miles Jordan added a comment - This is a funny one. I had this problem just now with version 2.0. I had two different layers with the same name but different namespaces. GetFeature would return this error using WFS 1.1.0 but was ok with version 1.0.0. I removed one of the layers and it started working. But then I tried to put it back to reproduce the problem and I couldn't reproduce it either! If I see it come up again I'll try a bit more to reproduce it.
Hide
Permalink
Andrea Aime added a comment -

Mass closing all issues that have been in "resolved" state for 2 months or more without any feedback or update

Show
Andrea Aime added a comment - Mass closing all issues that have been in "resolved" state for 2 months or more without any feedback or update

People

  • Assignee:
    Justin Deoliveira
    Reporter:
    Justin Deoliveira
Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: