-
-
Notifications
You must be signed in to change notification settings - Fork 99
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implemented support of XML and SOAP encoding for WMS 1.3.0 #598
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…upported WMS version
tfr42
added
feature
feature
and removed
in progress
enhancement
enhancement or improvement
labels
Oct 1, 2015
copierrj
added a commit
that referenced
this pull request
Oct 1, 2015
Implemented support of XML and SOAP encoding for WMS 1.3.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Support of XML and SOAP encoding was implemented for WMS 1.3.0. Following lines describe the enhancement (can also be found in the webservices handbook).
XML request encoding
A WMS 1.3.0 can be requested by HTTP POST (without any KVP) containing XML in request body. The provided XML has to be compliant to a specific XML schema depending on the requested operation.
The operations GetCapabilities, GetMap and GetFeatureInfo support XML request encoding.
The GetCapabilities XML request body has to be compliant to following schema: http://schemas.opengis.net/ows/2.0/owsGetCapabilities.xsd
The GetMap XML request body has to be compliant to following schema: http://schemas.opengis.net/sld/1.1/GetMap.xsd
The GetFeatureInfo XML request body has to be compliant to following schema: [1]
SOAP request encoding
The SOAP protocol can be used to request a WMS 1.3.0. SOAP 1.1 and 1.2 are supported.
A SOAP request is send via HTTP POST (without any KVP) and contains a XML request body. The request body consists of a SOAP envelope and a XML request body as described in chapter XML request encoding.
The operations GetCapabilities, GetMap and GetFeatureInfo support SOAP request encoding.
The support of the SOAP protocol by the WMS is described by an ExtendedCapabilities element in namespace http://schemas.deegree.org/extensions/services/wms/1.3.0.
The ExtendedCapabilities are compliant to following schema: [2]
New schemas
This pull request introduces two new schemas:
The schemas can be found in the handbook module (deegree-services/deegree-webservices-handbook/src/main/sphinx/xsd/), but they should also be uploaded to a publicly accessible location (e.g. web server). This issue should be discussed.
Examples
GetCapabilities XML request body example (can be used with Utah example workspace): [3]
GetMap XML request body example (can be used with Utah example workspace): [4]
GetFeatureInfo XML request body example (can be used with Utah example workspace): [5]
GetCapabilities SOAP request body example (can be used with Utah example workspace): [6]
[1]
[2]
[3]
[4]
[5]
[6]