Hi,
I have a mandate to create a geoserver module that functions as a interface to a preference store. I intend to design the module so that the actual store backing can be easily replaced depending on the requirements. The implementation I will do will back onto hibernate but the interface will be very simple and can easily implemented for other back-ends such as a file.
This is a proposal to add the module to the geoserver code base if the community would like to have this service module.
Jesse
Jesse Eichar wrote:
Hi,
I have a mandate to create a geoserver module that functions as a interface to a preference store. I intend to design the module so that the actual store backing can be easily replaced depending on the requirements. The implementation I will do will back onto hibernate but the interface will be very simple and can easily implemented for other back-ends such as a file.
This is a proposal to add the module to the geoserver code base if the community would like to have this service module.
In the absence of the PSC forming quite yet, we will assume this proposal is accepted.
And I quote:
groldan it is accepted
Jesse_Eichar77 woo hoo! I win!
Jesse_Eichar77 
Thanks
Cheers,
Jody
Are you talking about replacing the config.xml file?
I'm not sure we need something else. There haven't really been any complaints with reading the config files. And accessing the data in te file is already pretty easy and works great.
I just worry about over-designing something that is already working. But we should take a look at it. And if we were to use it, I would like to see a default implementation of a file access interface alongside the database-backed one.
Brent Owens
(The Open Planning Project)
Jesse Eichar wrote:
Hi,
I have a mandate to create a geoserver module that functions as a interface to a preference store. I intend to design the module so that the actual store backing can be easily replaced depending on the requirements. The implementation I will do will back onto hibernate but the interface will be very simple and can easily implemented for other back-ends such as a file.
This is a proposal to add the module to the geoserver code base if the community would like to have this service module.
Jesse
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Instead of assuming right away, lets wait for some more feedback.
Brent Owens
(The Open Planning Project)
Jody Garnett wrote:
Jesse Eichar wrote:
Hi,
I have a mandate to create a geoserver module that functions as a interface to a preference store. I intend to design the module so that the actual store backing can be easily replaced depending on the requirements. The implementation I will do will back onto hibernate but the interface will be very simple and can easily implemented for other back-ends such as a file.
This is a proposal to add the module to the geoserver code base if the community would like to have this service module.
In the absence of the PSC forming quite yet, we will assume this proposal is accepted.
And I quote:
groldan it is accepted
Jesse_Eichar77 woo hoo! I win!
Jesse_Eichar77 Thanks
Cheers,
Jody
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
Brent Owens wrote:
Instead of assuming right away, lets wait for some more feedback.
Brent we are on a time line, hence setting up a PSC was needed promptly. Sorry to rush, but if you want input into the project we got to get those procedures established and working. This was the first opportunity their will be more.
From my perspective I am trying to kick as much work from a commercial project out into the open source community, geotools and uDig are ready to catch content - and I think we are almost ready on the GeoServer side.
Cheers,
Jody
Brent Owens wrote:
Are you talking about replacing the config.xml file?
Nope.
I'm not sure we need something else. There haven't really been any complaints with reading the config files. And accessing the data in te file is already pretty easy and works great.
They asked some questions during the meeting, think you will find this one answered.
I just worry about over-designing something that is already working. But we should take a look at it. And if we were to use it, I would like to see a default implementation of a file access interface alongside the database-backed one.
I would rather see an implementation that worked (and shipped with) with hsql - that way
we would not have to relax query ability.
Jody
I agree with Jody on this one. We dont have the PSC formed yet and the proposal process outlined so its not really appropriate to treat this as an official proposal.
So why dont we give Jesse a community module and let him hack away, it wont impact the codebase. However I assume that in building your module you will require some changes to the core codebase, we can deal with them as they come.
-Justin
Jody Garnett wrote:
Jesse Eichar wrote:
Hi,
I have a mandate to create a geoserver module that functions as a interface to a preference store. I intend to design the module so that the actual store backing can be easily replaced depending on the requirements. The implementation I will do will back onto hibernate but the interface will be very simple and can easily implemented for other back-ends such as a file.
This is a proposal to add the module to the geoserver code base if the community would like to have this service module.
In the absence of the PSC forming quite yet, we will assume this proposal is accepted.
And I quote:
groldan it is accepted
Jesse_Eichar77 woo hoo! I win!
Jesse_Eichar77 Thanks
Cheers,
Jody
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
!DSPAM:1004,448f174d56671995013331!
--
Justin Deoliveira
jdeolive@anonymised.com
The Open Planning Project
http://topp.openplans.org