[
https://issues.apache.org/jira/browse/GEODE-7076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darrel Schneider updated GEODE-7076:
------------------------------------
Summary: Pdx should not have group, groups (was: Pdx should not have
group, groups, and uri)
> Pdx should not have group, groups
> ---------------------------------
>
> Key: GEODE-7076
> URL: https://issues.apache.org/jira/browse/GEODE-7076
> Project: Geode
> Issue Type: Improvement
> Components: management
> Reporter: Gang Yan
> Assignee: Darrel Schneider
> Priority: Major
>
> For REST API V2 for management, Swagger shows that the model for Pdx includes
> "group", "groups" and "uri".
> None of these should be specified when doing a POST Pdx. If you do specify
> group you get an error saying Pdx is only at the cluster level.
> uri also does not add any value on a POST, and if we do add support for GET
> to Pdx, it really isn't needed either since they had to do a GET on the uri
> itself so we don't need to tell them what the uri is.
> The uri comes from: org.apache.geode.management.api.RestfulEndpoint.getUri().
> Could the Pdx class override this and mark it with @JsonIgnore?
> group and groups comes from CacheElement. Could the Pdx class override them
> and mark them with @JsonIgnore?
> The java-api exposes these on Pdx and it would be best if it didn't. If we
> did some refactoring so that Pdx did not have these methods on it them this
> would clean up the rest-api automatically.
> Objective:
> # find a way to hide these attributes from Swagger docs.
> # is there a way to hide "group"/"groups" from the java api as well
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
