Hi,
On Tue, Oct 2, 2012 at 3:00 PM, Carlo Cancellieri
<ccancelli...@hotmail.com> wrote:
>> And in addition, you could also add a "version" property next to
>> "layerDescriptions", with the ServiceExceptionReport's "version"
>> attribute as value.
>
> The version I could append is the same as the protocol version, I've no
> information about the ExceptionHandler if no exception is returned (in this
> case it is the same 1.1.1).
Sorry for the confusion. The "ServiceExceptionReport" was a typo on my
end - 1.1.1 is fine.
>> Yes, but the typeName is missing. "typeName" is the "typename"
>> attribute of the Query node, and "layerName" is the "name" attribute
>> of the LayerDescription.
>
> I'm not sure about the Query node is the same as the layerName on my point
> of view, right?
In GeoServer it is the same, but the spec allows WMS layer names to be
mapped to different WFS/WCS type names.
> I'll get:
> {
> "version":"1.1.1"
> "layerDescriptions":
> [
> {
> "layerName": "cite:Lakes",
>
> "owsURL":
> "http://localhost:8080/geoserver/wfs/WfsDispatcher?";,
> "owsType": "WFS"
> "typeName": "cite:Lakes",
> },
> {
> "layerName": "cite:Forests",
>
> "owsURL":
> "http://localhost:8080/geoserver/wfs/WfsDispatcher?";,
> "owsType": "WFS"
> "typeName": "cite:Forests",
> }
> ]
> }
Perfect.
> For Exceptions:
>
>> {
>> "exceptions": [
>> {
>> "code": "InvalidParameterValue",
>> "text": "Could not find type name foobar"
>> }
>> ]
>> }
Also perfect.
> is there a problem if i add the "locator" attribute?:
> {
> "exceptions": [
> {
> "code": "InvalidParameterValue",
> "text": "Could not find type name foobar"
> "locator": "typeName"
> }
> ]
> }
Extra attributes don't hurt - you can definitely add them.
Thanks again,
Andreas.
>
> thanks for feedback,
> Carlo
>
>> Date: Tue, 2 Oct 2012 13:07:27 +0200
>
>> Subject: Re: [Geoserver-devel] GSIP 79 - Json support and WFS and WMS
>> ExceptionHandlers
>> From: ahoce...@opengeo.org
>> To: ccancelli...@hotmail.com
>> CC: geoserver-devel@lists.sourceforge.net
>
>>
>> Hey Carlo,
>>
>> see answers inline.
>>
>> On Mon, Oct 1, 2012 at 5:15 PM, Carlo Cancellieri
>> <ccancelli...@hotmail.com> wrote:
>> > so this is what are you asking for, right?
>> >
>> > * {"layerDescriptions":
>> > * [
>> > * {
>> > * "layerName": "cite:Lakes",
>> > * "owsURL":
>> > "http://localhost:8080/geoserver/wfs/WfsDispatcher?";,
>> > * "owsType": "WFS"
>> > * },
>> > * {
>> > * "layerName": "cite:Forests",
>> > * "owsURL":
>> > "http://localhost:8080/geoserver/wfs/WfsDispatcher?";,
>> > * "owsType": "WFS"
>> > * }
>> > * ]
>> > * }
>>
>> Yes, but the typeName is missing. "typeName" is the "typename"
>> attribute of the Query node, and "layerName" is the "name" attribute
>> of the LayerDescription.
>>
>> And in addition, you could also add a "version" property next to
>> "layerDescriptions", with the ServiceExceptionReport's "version"
>> attribute as value.
>>
>> > And what about an Exception like this?
>> >
>> >
>> > {"exceptionCode":"InvalidParameterValue","exceptionLocator":"typeName","exceptionText":"Could
>> > not find type name foobar"})
>>
>> Well, OpenLayers also has an OGC Exception format parser, and it would
>> be nice if we could share the format here as well. This is an example
>> object from the output of OpenLayers.Format.OGCExceptionReport:
>>
>> {
>> "exceptions": [
>> {
>> "code": "InvalidParameterValue",
>> "text": "Could not find type name foobar"
>> }
>> ]
>> }
>>
>> Note that "exceptions" is an array.
>>
>> Let me know if you have more questions.
>>
>> Andreas.
>>
>> >
>> > Thank you,
>> > Carlo
>> >
>> >> Date: Fri, 7 Sep 2012 19:24:39 +0200
>> >
>> >> Subject: Re: [Geoserver-devel] GSIP 79 - Json support and WFS and WMS
>> >> ExceptionHandlers
>> >> From: ahoce...@opengeo.org
>> >> To: ccancelli...@hotmail.com
>> >
>> >>
>> >> On Fri, Sep 7, 2012 at 7:23 PM, Andreas Hocevar <ahoce...@opengeo.org>
>> >> wrote:
>> >> > I should add though that it will probably make sense to have
>> >> > GeoServer
>> >> > return an object with a layerDescription property
>> >>
>> >> And I guess layerDescriptions would be an appropriate name - plural for
>> >> arrays.
>> >>
>> >> Andreas.
>>
>>
>>
>> --
>> Andreas Hocevar
>> OpenGeo - http://opengeo.org/
>> Expert service straight from the developers.
--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
------------------------------------------------------------------------------
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
