Support NAMESPACE parameter in WFS 1.1.0 KVP requests
-----------------------------------------------------
Key: GEOS-3306
URL: http://jira.codehaus.org/browse/GEOS-3306
Project: GeoServer
Issue Type: Bug
Components: WFS
Affects Versions: 1.7.5
Reporter: Tim Schaub
Assignee: Andrea Aime
Page 96 of the WFS 1.1.0 spec describes the NAMESPACE parameter as an optional
parameter common to WFS requests.
It looks to me like the following should work:
{noformat}
GET
/geoserver/wfs?version=1.1.0&request=DescribeFeatureType&typename=foo:archsites&namespace=xmlns(foo%3Dhttp%3A%2F%2Fwww.openplans.org%2Fspearfish)
{noformat}
(though the WFS doc doesn't specify that the = should be properly encoded)
With GeoServer 1.7.5, this is what I get:
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<ows:ExceptionReport version="1.0.0"
xsi:schemaLocation="http://www.opengis.net/ows
http://localhost:8080/geoserver/schemas/ows/1.0.0/owsExceptionReport.xsd";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:ows="http://www.opengis.net/ows";>
<ows:Exception exceptionCode="NoApplicableCode">
<ows:ExceptionText>Unknown namespace [foo]</ows:ExceptionText>
</ows:Exception>
</ows:ExceptionReport>
{code}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
