[Geoserver-users] GSIP 4 - Status Interface

GeoServer GeoServer User
1

Hi,

I have put together a new improvement proposal where I state my
intentions to have some of the GeoServer modules implement a Status
interface, which allows them to report their current status (stopped or
started) and any associated errors. This will allow a remote client to
query the GeoServer to ensure that all required modules are running.

I invite you to make comments on it here:
http://docs.codehaus.org/display/GEOS/GSIP+4+-+Status+Interface

Richard

PS. I apologize if it's not very complete or coherent right now. Quite
exhausted from moving and having trouble concentrating :slight_smile:

2

Very good … a first step towards the JMX :slight_smile:

On 8/22/06, Richard Gould <rgould@anonymised.com> wrote:

Hi,

I have put together a new improvement proposal where I state my
intentions to have some of the GeoServer modules implement a Status
interface, which allows them to report their current status (stopped or
started) and any associated errors. This will allow a remote client to
query the GeoServer to ensure that all required modules are running.

I invite you to make comments on it here:
http://docs.codehaus.org/display/GEOS/GSIP+4±+Status+Interface

Richard

PS. I apologize if it’s not very complete or coherent right now. Quite
exhausted from moving and having trouble concentrating :slight_smile:

Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

–

Eng. Alessio Fabiani
Vice President/CTO GeoSolutions

http://www.geo-solutions.it

3

Hi Richard,

This will be very cool!! I made some comments on the page and provided
some feedback. Will sum up here. This basically looks like something
very simple that provides the same functionality as JMX. So I am weary
about having GeoServer components implement interfaces that we have
rolled on our own. Instead it would be nice to reverse the dependency,
and make Status and Modules wrappers that accept components, the
components being plain old java objects. This makes it trivial to swap
in another technology when someone gets the time to do the JMX research.

-Justin

Richard Gould wrote:

Hi,

I have put together a new improvement proposal where I state my
intentions to have some of the GeoServer modules implement a Status
interface, which allows them to report their current status (stopped or
started) and any associated errors. This will allow a remote client to
query the GeoServer to ensure that all required modules are running.

I invite you to make comments on it here:
http://docs.codehaus.org/display/GEOS/GSIP+4+-+Status+Interface

Richard

PS. I apologize if it's not very complete or coherent right now. Quite
exhausted from moving and having trouble concentrating :slight_smile:

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:1004,44ea3c7457161702038478!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com

4

We had the same suggestion in the Skype meeting yesterday, ... Richard any chance you can set an IRC breakout time on this subject? (Alessio was going to email you the request).

Justin I think we have structured it the way you requested... modules is the api we are going to check, and Status is the "components" it is going to accept.

You are correct that we should treat the lifecycle question as a separate problem ... so how about it Justin how do we ask GeoServer to "reload"?

interface Module { String getID();
     shutdown();
}
interface Configurable extends Module {
     load( Settings settings, File dataDirectory );
     save( Settings settings, File dataDirectory );
}

And we just call make use of those callbacks during a create/load/save/dispose lifecycle?

Justin if you get some time to chat I would like to try and recreate the various stepping stones a module can cross as it grows up for eventual inclusion in GeoServer.
Jody

Hi Richard,

This will be very cool!! I made some comments on the page and provided
some feedback. Will sum up here. This basically looks like something
very simple that provides the same functionality as JMX. So I am weary
about having GeoServer components implement interfaces that we have
rolled on our own. Instead it would be nice to reverse the dependency,
and make Status and Modules wrappers that accept components, the
components being plain old java objects. This makes it trivial to swap
in another technology when someone gets the time to do the JMX research.

-Justin

Richard Gould wrote:
  

Hi,

I have put together a new improvement proposal where I state my
intentions to have some of the GeoServer modules implement a Status
interface, which allows them to report their current status (stopped or
started) and any associated errors. This will allow a remote client to
query the GeoServer to ensure that all required modules are running.

I invite you to make comments on it here:
http://docs.codehaus.org/display/GEOS/GSIP+4+-+Status+Interface

Richard

PS. I apologize if it's not very complete or coherent right now. Quite
exhausted from moving and having trouble concentrating :slight_smile:

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:1004,44ea3c7457161702038478!

5

Hi Jody,

My main concern was to not have geoserver start implementing these
interfaces all over the place. It makes all of our code dependent on
these interfaces we have rolled our own. And when it comes time and we
may want to do things with JMX,

My other concern is the inventing of our own plugin framework when there
are alternatives available.

I included some comments on the GSIP as to how I thought you could leave
the core of geoserver alone and still pull this off. Its very similar to
how spring publishes beans with JMX.

-Justin

Jody Garnett wrote:

We had the same suggestion in the Skype meeting yesterday, ... Richard
any chance you can set an IRC breakout time on this subject? (Alessio
was going to email you the request).

Justin I think we have structured it the way you requested... modules is
the api we are going to check, and Status is the "components" it is
going to accept.

You are correct that we should treat the lifecycle question as a
separate problem ... so how about it Justin how do we ask GeoServer to
"reload"?

interface Module { String getID();
    shutdown();
}
interface Configurable extends Module {
    load( Settings settings, File dataDirectory );
    save( Settings settings, File dataDirectory );
}

And we just call make use of those callbacks during a
create/load/save/dispose lifecycle?

Justin if you get some time to chat I would like to try and recreate the
various stepping stones a module can cross as it grows up for eventual
inclusion in GeoServer.
Jody

Hi Richard,

This will be very cool!! I made some comments on the page and provided
some feedback. Will sum up here. This basically looks like something
very simple that provides the same functionality as JMX. So I am weary
about having GeoServer components implement interfaces that we have
rolled on our own. Instead it would be nice to reverse the dependency,
and make Status and Modules wrappers that accept components, the
components being plain old java objects. This makes it trivial to swap
in another technology when someone gets the time to do the JMX research.

-Justin

Richard Gould wrote:

Hi,

I have put together a new improvement proposal where I state my
intentions to have some of the GeoServer modules implement a Status
interface, which allows them to report their current status (stopped or
started) and any associated errors. This will allow a remote client to
query the GeoServer to ensure that all required modules are running.
I invite you to make comments on it here:
http://docs.codehaus.org/display/GEOS/GSIP+4+-+Status+Interface

Richard

PS. I apologize if it's not very complete or coherent right now. Quite
exhausted from moving and having trouble concentrating :slight_smile:

-------------------------------------------------------------------------

Using Tomcat but need to do more? Need to support web services,
security?
Get stuff done quickly with pre-integrated technology to make your
job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache
Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

!DSPAM:1004,44ec0b6d204181510810322!

--
Justin Deoliveira
The Open Planning Project
jdeolive@anonymised.com