Hello devs, I am using GeoServer 1.6.3 as WFS with Mapbender. Mapbender offers a digitize functionality. Everything worked fine with previous versions. Now with GeoServer 1.6.2 the SchemaLocation-definition in the Transaction-Request needs the describeFeatureType-Request (this is fine and follows the OGC WFS Standard).
So we added the Request to the Transaction. (as we know the describeFeaturType-Request from the onlineresource). This was something like: http://localhost:8080/geoserver/wfs?request=DescribeFeatureType&typename=topp:tasmania_roads But GeoServer expects the request like: http://localhost:8080/geoserver/wfs/DescribeFeatureType?typename=topp:tasmania_roads The problem is that the POST-ONLINESESOURCE definition in the getCapabilities-request says. ------------------- <DescribeFeatureType> <SchemaDescriptionLanguage> <XMLSCHEMA/> </SchemaDescriptionLanguage> <DCPType> <HTTP> <Get onlineResource="http://localhost:8080/geoserver/wfs?request=DescribeFeatureType"/> </HTTP> </DCPType> <DCPType> <HTTP> <Post onlineResource="http://localhost:8080/geoserver/wfs?"/> </HTTP> </DCPType> </DescribeFeatureType> ---------------------------------- This is what the client uses. I think this is a bug. You should change the POST-ONLINESESOURCE definition for the describefeatureType in the getCapabilities-request to "http://localhost:8080/geoserver/wfs/DescribeFeatureType?";. Or even better: accept to use the GET-Request in the Transaction-request. What do you think about this? astrid -- Best regards Astrid Emde ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
