Fix bug in WPS client: LiteralInputType is missing DefaultValue property #810
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.
This request fixes a bug in the WPS client:
Currently, LiteralInputType doesn't handle a literal input's default value which can be announced by a WPS server with the
<DefaultValue>
tag in the ProcessDescriptions, see Web Processing Service standard version 1.0.0, Table 25 (page 26).This fix adds a property for it to LiteralInputType and adapts ProcessDetails to parse it from the ProcessDescriptions.
It also adds an optional unit test that is run if demo_wps_url2 and demo_wps_def_processor are set in .deegree-test.properties. These values have to refer to a processor that has at least one default value for a literal input, e.g. http://www.zoo-project.org/cgi-bin/zoo_loader.cgi?Service=WPS&Version=1.0.0&Request=GetCapabilities and raster-tools-src.cgi-env.Gdal_Warp