Introduce Conformance API to configure OGCAPI Features#8014
Introduce Conformance API to configure OGCAPI Features#8014jodygarnett merged 21 commits intogeoserver:mainfrom
Conversation
59c7f4b to
42d106c
Compare
aaime
left a comment
There was a problem hiding this comment.
I like the initial idea, looking forward to see some GUI to configure, how it's stored, and how it's eventually used to control the service behavior.
Left a bunch of comments below.
src/community/ogcapi/ogcapi-core/src/main/java/org/geoserver/ogcapi/APIConformance.java
Outdated
Show resolved
Hide resolved
src/community/ogcapi/ogcapi-core/src/main/java/org/geoserver/ogcapi/APIConformance.java
Outdated
Show resolved
Hide resolved
src/community/ogcapi/ogcapi-core/src/main/java/org/geoserver/ogcapi/ConformanceInfo.java
Outdated
Show resolved
Hide resolved
...ty/ogcapi/ogcapi-features/src/main/java/org/geoserver/ogcapi/v1/features/FeatureService.java
Outdated
Show resolved
Hide resolved
src/web/core/src/test/java/org/geoserver/web/admin/StatusPageTest.java
Outdated
Show resolved
Hide resolved
7c327c2 to
1dd5158
Compare
aaime
left a comment
There was a problem hiding this comment.
Had a look and provided some comments. Will be interesting to see how you want to address turning off some behavior. Or are you settling down to just stop advertising it, but then leave it there?
...y/ogcapi/ogcapi-features/src/main/java/org/geoserver/ogcapi/v1/features/CQL2Conformance.java
Outdated
Show resolved
Hide resolved
...y/ogcapi/ogcapi-features/src/test/java/org/geoserver/ogcapi/v1/features/ConformanceTest.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
I did not expect to see this page hand-written... actually it might be a problem.
What if a given conformance class is provided through a plugin?
Probably better to have enough configuration to auto-generate this from the conformance classes that might be found in the spring context.
There was a problem hiding this comment.
I am walking before I can run on this one Andrea. I think the next step is to make a conformance panel that can be used multiple times.
Want to get something that functions at all here to control the module.
There was a problem hiding this comment.
If a conformance class is provided through a plugin it provides its own AdminPagePanel, as that is the existing UI infrastructure for contributing.
There was a problem hiding this comment.
That is one possibility, but it's work-intensive and clumsy. Alsor remember admin panels are not following an order, you can have panels out of any logical order, and other unrelated extensions have their eventual panel show up in the middle.
There was a problem hiding this comment.
I am thinking how to do that, and we have an extension that provides:
- APIConformance being configured
- property expression
metadata/cql2/textfrom WFSInfo
Then FeatureServiceAdminPanel could do the very simple story we have now. But not additional settings.
May be better to have an extension like ConformancePanel, with a default implementation for the simple case.
b14d6ea to
558c349
Compare
7159088 to
215fc7c
Compare
aaime
left a comment
There was a problem hiding this comment.
Had another go looking at the diff (but could not try it out interactively yet)
...y/ogcapi/ogcapi-features/src/main/java/org/geoserver/ogcapi/v1/features/CQL2Conformance.java
Outdated
Show resolved
Hide resolved
...ty/ogcapi/ogcapi-features/src/main/java/org/geoserver/ogcapi/v1/features/FeatureService.java
Outdated
Show resolved
Hide resolved
...gcapi/ogcapi-features/src/main/java/org/geoserver/ogcapi/v1/features/FeatureConformance.java
Outdated
Show resolved
Hide resolved
...rc/main/java/org/geoserver/ogcapi/v1/features/FeatureServiceXStreamPersisterInitializer.java
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Based on configuration, the sortby, filter, filter-lang parameters should also be removed (and so on)
There was a problem hiding this comment.
path: search, queryables and functions now removable
parameters: filter, filter-lang, sortBy now removable
...ogcapi/ogcapi-core/src/main/java/org/geoserver/ogcapi/OGCAPIXStreamPersisterInitializer.java
Outdated
Show resolved
Hide resolved
...ity/ogcapi/web-features/src/main/java/org/geoserver/ogcapi/web/FeatureServiceAdminPanel.java
Outdated
Show resolved
Hide resolved
f67a98a to
df36c0e
Compare
This repalce status and provides concepts such as COMMUNITY_STANDARD and RETIRED_STANDARD
The checkboxes in FeatureServiceAdminPanel would otherwise update the model value to false when it was originally null. This way the XStream persister will get the unchanged values as null instead of false.
e065fce to
362c961
Compare
|
Rebased to get the cite fixes from main branch. Addressed formatting and QA failures also. |
Looking at how to add conformance to the ogcapi-core as something we can configure on and off.
Registers an AdminPagePanel with WFSInfo to be shown on the WFS page:
Feedback welcome.
Checklist
mainbranch (backports managed later; ignore for branch specific issues).For core and extension modules:
[GEOS-XYZWV] Title of the Jira ticket.