Hi Ben,
We added the secondary namespace and all is well. Very interesting that it
affected GetFeature but not GetPropertyValue.
Thanks!
-Gavin
On Fri, Jul 28, 2017 at 6:14 PM, Ben Caradoc-Davies <[email protected]>
wrote:
> Gavin,
>
> both of these problems are likely caused by the lack of a secondary
> namespace.
>
> I saw the difference in encoding (the xmlns on the non-root element),
> which is odd. Incremental improvements might have changed the manifestation
> of the problem (no longer an exception), and implementation differences
> might explain the difference between the two requests. Time for a
> documentation update.
>
> Please add a secondary namespace gml for GML 3.2.1 and report back. Any
> further app-schema misbehaviour is likely a bug.
>
> Kind regards,
> Ben.
>
>
> On 29/07/17 11:24, Gavin Medley wrote:
>
>> Hi Ben,
>>
>> That's probably what it is. I don't have a secondary namespace for gml.
>> Weird that it's not throwing an error when encoding the response.
>>
>> With respect to your second question, we do see wfs:FeatureCollection and
>> wfs:ValueCollection when using App Schema. However, in the
>> wfs:FeatureCollection, we are missing the namespace definition for gml. In
>> wfs:ValueCollection we see
>> xmlns:gml="http://www.opengis.net/gml/3.2";
>> Do you think this is likely due to the lack of secondary namespace?
>>
>>
>> -Gavin
>>
>> On Fri, Jul 28, 2017 at 4:57 PM, Ben Caradoc-Davies <[email protected]>
>> wrote:
>>
>> Gavin,
>>>
>>> that is very interesting. My guess is that the different response root
>>> elements end up with different namespace configurations being provided to
>>> the GeoTools encoder.
>>>
>>> Have you defined a secondary namespace for the gml prefix?
>>> http://docs.geoserver.org/latest/en/user/data/app-schema/
>>> supported-gml-versions.html#secondary-namespace-for-gml-3-2-1-required
>>>
>>> A secondary namespace was not required for GML 3.1.1 application schemas
>>> because WFS 1.1.0 was defined in terms of GML 3.1.1. WFS 2.0.0 is
>>> GML-version-agnostic, so the encoder no longer has a namespace prefix
>>> binding to use.
>>>
>>> GetFeature responses have a root element of wfs:FeatureCollection.
>>> GetPropertyValue responses have a root element of wfs:ValueCollection. Do
>>> you see these with app-schema?
>>>
>>> Kind regards,
>>> Ben.
>>>
>>> On 29/07/17 10:05, Gavin Medley wrote:
>>>
>>> Hi,
>>>>
>>>> I think this is a bug, probably in App Schema, but I want to ensure I'm
>>>> not
>>>> doing something wrong before filing a report. I am using App Schema to
>>>> output GeodesyML for WFS requests. I noticed recently that Geoserver
>>>> fails
>>>> to resolve one of my namespaces in GetFeature requests. This confused me
>>>> because in the past it wasn't a problem. Now I am further confused
>>>> because
>>>> in GetPropertyValue requests it resolves again! How can one WFS request
>>>> fail to resolve a namespace but another succeeds? To be clear these are
>>>> back to back requests with zero change to mapping files or any other
>>>> configuration.
>>>>
>>>> *Specifics:*
>>>>
>>>> http://host:port/geoserver/ows?
>>>> service=WFS&
>>>> version=2.0.0&
>>>> request=*GetFeature*&
>>>> typeNames=geo:siteLog&
>>>> outputFormat=gml32&
>>>> count=10
>>>>
>>>> *results in*
>>>>
>>>> <geo:siteLocation>
>>>> <geo:countryCodeISO>Nepal</geo:countryCodeISO>
>>>> <geo:tectonicPlate>Eurasia</geo:tectonicPlate>
>>>> <geo:approximatePositionITRF>
>>>> <geo:cartesianPosition>
>>>> <*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
>>>> cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>
>>>> </geo:cartesianPosition>
>>>> <geo:geodeticPosition>
>>>> <*null:Point* xmlns:null="http://www.opengis.net/gml/3.2"; id="
>>>> latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-4128"/>
>>>> </geo:geodeticPosition>
>>>> </geo:approximatePositionITRF>
>>>> </geo:siteLocation>
>>>>
>>>> *BUT*
>>>>
>>>> http://ws-beta.int.unavco.org:9090/geoserver/wfs?
>>>> service=wfs&
>>>> version=2.0.0&
>>>> request=*GetPropertyValue*&
>>>> typeNames=geo:siteLog&
>>>> valueReference=geo:siteLocation&
>>>> count=10
>>>>
>>>> *results in*
>>>>
>>>> <geo:siteLocation>
>>>> <geo:countryCodeISO>Nepal</geo:countryCodeISO>
>>>> <geo:tectonicPlate>Eurasia</geo:tectonicPlate>
>>>> <geo:approximatePositionITRF>
>>>> <geo:cartesianPosition>
>>>> <*gml:Point* gml:id="
>>>> cartesian.geoml_monuments.fid--1f0f9389_15d8afee8b4_-40bc"/>
>>>> </geo:cartesianPosition>
>>>> <geo:geodeticPosition>
>>>> <*gml:Point* gml:id="latlon.geoml_monuments.fid--1f0f9389_15d8afee8b4_-
>>>> 40bc"
>>>> />
>>>> </geo:geodeticPosition>
>>>> </geo:approximatePositionITRF>
>>>> </geo:siteLocation>
>>>>
>>>>
>>>> Many thanks,
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------
>>>> ------------------
>>>> Check out the vibrant tech community on one of the world's most
>>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Geoserver-users mailing list
>>>>
>>>> Please make sure you read the following two resources before posting to
>>>> this list:
>>>> - Earning your support instead of buying it, but Ian Turton:
>>>> http://www.ianturton.com/talks/foss4g.html#/
>>>> - The GeoServer user list posting guidelines:
>>>> http://geoserver.org/comm/userlist-guidelines.html
>>>>
>>>> [email protected]
>>>> https://lists.sourceforge.net/lists/listinfo/geoserver-users
>>>>
>>>>
>>>> --
>>> Ben Caradoc-Davies <[email protected]>
>>> Director
>>> Transient Software Limited <http://transient.nz/>
>>> New Zealand
>>>
>>>
>>
>>
>>
> --
> Ben Caradoc-Davies <[email protected]>
> Director
> Transient Software Limited <http://transient.nz/>
> New Zealand
>
--
Gavin Medley
Software Engineer I
*UNAVCO*
6350 Nautilus Drive
Boulder, CO 80301-5394
[email protected]
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
