Add NAMESPACE KVP Parameter when communicating to DeeGree WFS
-------------------------------------------------------------

                 Key: GEOT-1740
                 URL: http://jira.codehaus.org/browse/GEOT-1740
             Project: GeoTools
          Issue Type: New Feature
          Components: data wfs
    Affects Versions: 2.4.2, 2.5-M1
            Reporter: Jody Garnett
            Assignee: David Zwiers
             Fix For: 2.4.2


The following is from email on the uDig-devel list; Tore is setting up a 
Deegree server configured for communication with WFS 1.0 clients:

OpenJump with the WFS plugin create a DescribeFeatureType request like:
{panel}
?SERVICE=WFS&REQUEST=DescribeFeatureType&version=1.0.0&TYPENAME=app:MYFT&NAMESPACE=xmlns(app=http://www.deegree.org/app)
{panel}

uDig create a DescribeFeatureType request like:
{panel}
?SERVICE=WFS&VERSION=1.0.0&REQUEST=DescribeFeatureType&TYPENAME= app:MYFT 
{panel}

A bit of research shows that GeoTools is doing the right thing here, NAMESPACE 
while useful looks to be a vendor specific parameter not mentioned in the 
specification. Perhaps it is part of the generic Open Web Services 
specification?

To proceed on this one we could add the *NAMESPACE* KVP parameter to the non 
strict wfs stratagy object and hope for the best. It is only worth fixing this 
bug if a user is available for testing.

-- 
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

        

-------------------------------------------------------------------------
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/
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to