Thanks to everyone who has responded, looks like you are good to go on this
one.
--
Jody Garnett
On 22 March 2016 at 15:28, Morgan Thompson
wrote:
> GSIP-143 proposes adding the ability to report basic status information
> about installed Geoserver extensions. This information could be reported
+1. Looks quite handy.
On 23/03/16 11:28, Morgan Thompson 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-
t;>> > Hi,
> >>> >
> >>> > Not a voting member, but I would be ok with either
> ConfigurationStatus
> >>> > or
> >>> > ComponentStatus. However, I would lean more towards
> >>> > ConfigurationStatus
> >>
preference.
>>> >
>>> > Chris Snider
>>> > Senior Software Engineer
>>> > Intelligent Software Solutions, Inc.
>>> >
>>> >
>>> > -Original Message-
>>> > From: Ben Caradoc-Davies [mailto:b...@trans
t; Senior Software Engineer
>> > Intelligent Software Solutions, Inc.
>> >
>> >
>> > -Original Message-
>> > From: Ben Caradoc-Davies [mailto:b...@transient.nz]
>> > Sent: Tuesday, March 22, 2016 5:00 PM
>> > To: Jody Garnett ; M
tatus
> > if I get a preference.
> >
> > Chris Snider
> > Senior Software Engineer
> > Intelligent Software Solutions, Inc.
> >
> >
> > -Original Message-
> > From: Ben Caradoc-Davies [mailto:b...@transient.nz]
> > Sent: Tuesday, March 22, 2016 5:00 PM
> >
> >
> > -Original Message-
> > From: Ben Caradoc-Davies [mailto:b...@transient.nz]
> > Sent: Tuesday, March 22, 2016 5:00 PM
> > To: Jody Garnett ; Morgan Thompson
> >
> > Cc: Geoserver Developers
> > Subject: Re: [Geoserver-devel] GSI
Thompson <
> mthomp...@boundlessgeo.com>
> Cc: Geoserver Developers
> Subject: Re: [Geoserver-devel] GSIP-143 Extension Status
>
> Or ComponentStatus?
>
> On 23/03/16 11:48, Jody Garnett wrote:
> > The proposal is written as ExtensionStatus (makes sense as
utions, Inc.
>
>
> -Original Message-
> From: Ben Caradoc-Davies [mailto:b...@transient.nz]
> Sent: Tuesday, March 22, 2016 5:00 PM
> To: Jody Garnett ; Morgan Thompson
>
> Cc: Geoserver Developers
> Subject: Re: [Geoserver-devel] GSIP-143 Extension Status
&g
Caradoc-Davies [mailto:b...@transient.nz]
Sent: Tuesday, March 22, 2016 5:00 PM
To: Jody Garnett ; Morgan Thompson
Cc: Geoserver Developers
Subject: Re: [Geoserver-devel] GSIP-143 Extension Status
Or ComponentStatus?
On 23/03/16 11:48, Jody Garnett wrote:
> The proposal is written as ExtensionSta
Or ComponentStatus?
On 23/03/16 11:48, Jody Garnett wrote:
> 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
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 t
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
13 matches
Mail list logo
