Slight point of clarification - currently lists containing a mix of nulls
and objects are coming out as invalid JSON. The only observed place where
this happens is with LayerGroups (specifically the style list, where null
represents "use the default style").
Since the API-breaking fix is definitely not backportable, it might make
sense to apply the alternative fix to the current stable branch (although I
am not especially happy having that level of reflection anywhere in the
codebase)
I am happy to make a proposal for the "proper", API-breaking fix.
Torben
On Tue, Jan 31, 2017 at 10:38 AM, Jody Garnett <[email protected]>
wrote:
> Taking this pull request discussion to the email list as it has some
> strategic consequences - so we probably need a proposal.
>
> * https://github.com/geoserver/geoserver/pull/2072
> * https://osgeo-org.atlassian.net/browse/GEOS-7873
>
> Torben has two "fixes":
> - a good fix, updating the version of jettison - that breaks REST API
> compatibility (sigh)
> - a bad fix, using reflection to hack - produces valid JSON code but a
> brittle fix
>
> What would we like to do? Currently empty lists are coming out as invalid
> JSON.
> --
> Jody Garnett
>
> ------------------------------------------------------------
> ------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> _______________________________________________
> Geoserver-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
