Export original XML schema if exactly one local schema is configured #1068
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
tfr42
added
enhancement
|
As a TMC, we would prefer the sorting of the Java import statements to remain the same. |
|
The TMC agrees that limiting our use of more advanced XML schema features to deal with limited XML schema implementations in clients is a good thing. Therefore we endorse the proposed change. |
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.
If only one schema is configured in a FeatureStore, the schema is referenced in the local file system and DisableDynamicSchema is set to true, a DescribeFeatureType request returns the original XML schema instead of including the schema in a deegree generated schema via include.
Closes #1044.