WFS digitizing failed when using GeoServer 1.6.2 due to missing links in xsi:schemaLocation

[astrid_emde]

GeoServer 1.6.x is less tolerant concerning the xsi:schemaLocation values that has to be defined in the Transcation-Request. This follows the WFS 1.0.0 Specification.

The definition of the following values is also needed as schemaLocation-values:

• namespaceLocation of the FeatureType
• describeFeatureType-Request

[astrid_emde]

to solve the problem I added two values(namespaceLocation,DescribeFeatureType-request) to the SchemaLocation in the Transaction_Request.

This happened in two files:

• ./php/mod_wfs.php echo "wfs_conf.$i.wfs_describefeaturetype='".$rowwfs_describefeaturetype."';";)
• ./javascripts/wfs.js see function get_wfs_str(myconf, d, m, type, fid)

Have a look at the revision: ​http://trac.osgeo.org/mapbender/browser/branches/2.5/http/php/mod_wfs.php?rev=2455 ​http://trac.osgeo.org/mapbender/browser/branches/2.5/http/javascripts/wfs.js?rev=2456

[astrid_emde]

There is one thing you have to change, when you use GeoServer (seems to be a bug in GeoServer 1.6)

The Capabilities-document defines the Onlineresouce like this for Post and Get: ​http://localhost:8080/geoserver/wfs?request=DescribeFeatureType

But in the Transaction-request GeoServer only accepts the following SchemaLocation-value for DescribeFeaturetype. ​http://localhost:8080/geoserver/wfs/DescribeFeatureType?typename=topp:poi

How should Mapbender know this?

My workaround was to go to the Mapbender Database and change the colum wfs.wfs_describefeaturetype to --> ​http://localhost:8080/geoserver/wfs/DescribeFeatureType?

There will be a ticket in the GeoServer-trac to find a solution.

[astrid_emde]

news about Mapbender 2.5 and GeoServer 1.6.x

-> bugfixes for version 2.5

[astrid_emde]

I made a ticket in the GeoServer issue tracker:

​http://jira.codehaus.org/browse/GEOS-1938

[astrid_emde]

digitizing failed, when & appears in the schema-location of the transaction-request.

--> a solution would be to use the POST-Request definition from the Capabilities-document instead of the GET-definition. At the moment Mapbender always uses the GET values. This does not make sense as the scripts always use POST.

Change Request for WFS

When loading the WFS Mapbender imports the only the GET DCPType for each Request. But the Scripts use POST for the requests. It would make more sense to use the POST information from the Capabilities document from the beginning. If we need the GET Onlineresource too we should add new database columns to handle the different informations

[astrid_emde]

I tried it already: changed GET to POST in the file /classes/class_wfs.php

first testing shows that all the functionality is still working

--> wfs geoserver-transaction is now successfull

[astrid_emde]

I changed the code in class_wfs.php.