GeoFence integrated REST API won't accept as write what it produced in read

Description

The API was designed to use JAXB/Jackson on both encoding and decoding, but since the GeoServer REST upgrade the XStream converters will take precence on write, causing the two sides to handle encoding in a significantly different way.

Environment

None

Assignee

Unassigned

Reporter

Andrea Aime

Triage

None

Fix versions

None

Affects versions

None

Components

Priority

Medium
Configure