Thanks Morgan, proposal looks clear, +1
I have two interesting questions for you that may only be answerable once
you start work.
Is there any advantage to defining a naming convention for the bean ids
(say making them match jar name)?
The proposal is written as ExtensionStatus (makes sense as those are the
things users install), is their any advantage to calling it
ConfigurationStatus (so we can report on on things like RenderingEngine
from gs-main which is not properly an extension).
--
Jody Garnett
On 22 March 2016 at 15:28, Morgan Thompson <mthomp...@boundlessgeo.com>
wrote:
> GSIP-143 proposes adding the ability to report basic status information
> about installed Geoserver extensions. This information could be reported by
> the REST api in JSON format as well as on the server status page as per
> GEOS-6068.
>
> https://osgeo-org.atlassian.net/browse/GEOS-6068
> https://github.com/geoserver/geoserver/wiki/GSIP-143
>
> Morgan Thompson
> Junior Engineer | Boundless
> mthomp...@boundlessgeo.com
>
>
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
> _______________________________________________
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>
------------------------------------------------------------------------------
Transform Data into Opportunity.
Accelerate data analysis in your applications with
Intel Data Analytics Acceleration Library.
Click to learn more.
http://pubads.g.doubleclick.net/gampad/clk?id=278785351&iu=/4140
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
