[Geoserver-devel] Confused about SOAP version supported by WFS 2.0 on trunk

GeoServer GeoServer Developer
1

Hi all,
I'm reading the WFS 2.0 spec and the Dispatcher to figure out which SOAP version
the dispatcher is able to handle and I'm getting confused.

The WFS 2.0 spec in Annex D, section D.4.1 says:

------------------------------------------------------------------

The elements above are declared in the namespace for the SOAP envelope
version 1.1:
http://schemas.xmlsoap.org/soap/envelope/
Services that conform to this International Standard may optionally
support SOAP. For maximum interoperability, these
services shall support SOAP version 1.1 (see W3C SOAP) for web feature
service requests and responses.

------------------------------------------------------------------

So this means SOAP 1.1.

However if I look at the Dispatcher code on trunk I get:

static final String SOAP_NS = "http://www.w3.org/2003/05/soap-envelope";

That namespace is used instead by SOAP 1.2, and it is used for responses.

Now... the recognition of a SOAP request is mime type based,
application/soap+xml,
and it works so that the envelope is ignored, but the response is built with
http://www.w3.org/2003/05/soap-envelope, which makes me think
that even if we receive a SOAP 1.1 request we're going to respond with a
SOAP 1.2 envelope.

I guess this might be a bug... but what I'm trying to understand
better is, what
really changes moving from 1.1 to 1.2 in the context of OGC services?
Is it just a namespace declaration or there is more, maybe different
error reporting,
different HTTP headers?

Cheers
Andrea

--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

2

Hmmm… to be honest i am not sure. The “soap support” (if you can call it that) was done purely in order to tick a check box. It passed the clients acceptance tests so i never took it much further than that, so not surprised there are inconsistencies. I guess if the spec references SOAP 1.1 it would be best to work with that.

On Thu, Jul 5, 2012 at 7:04 AM, Andrea Aime <andrea.aime@anonymised.com> wrote:

Hi all,
I’m reading the WFS 2.0 spec and the Dispatcher to figure out which SOAP version
the dispatcher is able to handle and I’m getting confused.

The WFS 2.0 spec in Annex D, section D.4.1 says:

The elements above are declared in the namespace for the SOAP envelope
version 1.1:
http://schemas.xmlsoap.org/soap/envelope/
Services that conform to this International Standard may optionally
support SOAP. For maximum interoperability, these
services shall support SOAP version 1.1 (see W3C SOAP) for web feature
service requests and responses.

So this means SOAP 1.1.

However if I look at the Dispatcher code on trunk I get:

static final String SOAP_NS = “http://www.w3.org/2003/05/soap-envelope”;

That namespace is used instead by SOAP 1.2, and it is used for responses.

Now… the recognition of a SOAP request is mime type based,
application/soap+xml,
and it works so that the envelope is ignored, but the response is built with
http://www.w3.org/2003/05/soap-envelope, which makes me think
that even if we receive a SOAP 1.1 request we’re going to respond with a
SOAP 1.2 envelope.

I guess this might be a bug… but what I’m trying to understand
better is, what
really changes moving from 1.1 to 1.2 in the context of OGC services?
Is it just a namespace declaration or there is more, maybe different
error reporting,
different HTTP headers?

Cheers
Andrea

–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf

Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/

Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

3

On Thu, Jul 5, 2012 at 4:58 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:

Hmmm... to be honest i am not sure. The "soap support" (if you can call it
that) was done purely in order to tick a check box. It passed the clients
acceptance tests so i never took it much further than that, so not surprised
there are inconsistencies. I guess if the spec references SOAP 1.1 it would
be best to work with that.

I guess so. There is another bit though, this is generic
functionality, not WFS specific,
and other OGC protocols can be bound to SOAP 1.2, so I guess the right
way to do
it would be to recognize from the request which version of SOAP was
used, and respond accordingly

Cheers
Andrea

--
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead

Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy

phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549

http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf