Hi.
I'm working on the proxy module Dwins mentioned earlier. It will have a Wicket config UI, and will store configuration somewhere as well as access it during runtime.
What conventions are there for storing configuration information & accessing it during runtime?
Thanks,
Alan
Hi Alan,
It really depends on your use case. Some modules use their own file format, be it a property file, or xml file to do configuration. In which they just choose a location in the data directory to store it. This is typically what extensions do.
Other modules may want to tie directly into the configuration system, and come up with a class or model in which they want to use to persist whatever configuration they need to. Currently our configuration sub system only allows this pluggability with services. It probably needs to be extended to arbitrary entities.
It is up to you to choose, both have benefits. Since you are going to the trouble of building a UI, having an actual set of objects which you persist probably makes more sense, since this is how wicket works. However the extension points that you would need to this are not quite there, so it would take a bit of work on the core to enable this.
-Justin
Alan Gerber wrote:
Hi.
I'm working on the proxy module Dwins mentioned earlier. It will have a Wicket config UI, and will store configuration somewhere as well as access it during runtime.
What conventions are there for storing configuration information & accessing it during runtime?
Thanks,
Alan------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
The second option would be better for me. It's unfortunate to hear that it's unavailable to something other than a service.
Without having that option available to me, the option of using a file to share between the server and its configuration page is looking necessary. Actually implementing that looks like it'll be pretty hackish, though it should probably work alright. Would that be something it might make sense for me to try to look at? (I guess I don't know if Dwins has much else up his sleeve for me, so I should ask him that).
On Jun 30, 2009, at 8:38 PM, Justin Deoliveira wrote:
Hi Alan,
It really depends on your use case. Some modules use their own file format, be it a property file, or xml file to do configuration. In which they just choose a location in the data directory to store it. This is typically what extensions do.
Other modules may want to tie directly into the configuration system, and come up with a class or model in which they want to use to persist whatever configuration they need to. Currently our configuration sub system only allows this pluggability with services. It probably needs to be extended to arbitrary entities.
It is up to you to choose, both have benefits. Since you are going to the trouble of building a UI, having an actual set of objects which you persist probably makes more sense, since this is how wicket works. However the extension points that you would need to this are not quite there, so it would take a bit of work on the core to enable this.
-Justin
Alan Gerber wrote:
Hi.
I'm working on the proxy module Dwins mentioned earlier. It will have a Wicket config UI, and will store configuration somewhere as well as access it during runtime.
What conventions are there for storing configuration information & accessing it during runtime?
Thanks,
Alan
------------------------------------------------------------------------------
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Alan Gerber wrote:
The second option would be better for me. It's unfortunate to hear that it's unavailable to something other than a service.
Well it is certainly something we could look at doing on trunk as it is something that is needed. However as I understand it your module is on 1.7.x? It would be harder to pull this off there.
Without having that option available to me, the option of using a file to share between the server and its configuration page is looking necessary. Actually implementing that looks like it'll be pretty hackish, though it should probably work alright. Would that be something it might make sense for me to try to look at? (I guess I don't know if Dwins has much else up his sleeve for me, so I should ask him that).
You mean using the file? Or tying info the config system? I think you mean the latter. But yeah, it would be doable mostly because there are a few extensions that configure themselves in this way. The ogr extension is a good example. It uses a class to store all the necessary configration it needs (OgrConfiguration), and a class to read it from the data directory, Ogr2OgrConfigurator. You can probably draw some good inspiration from that.
On Jun 30, 2009, at 8:38 PM, Justin Deoliveira wrote:
Hi Alan,
It really depends on your use case. Some modules use their own file format, be it a property file, or xml file to do configuration. In which they just choose a location in the data directory to store it. This is typically what extensions do.
Other modules may want to tie directly into the configuration system, and come up with a class or model in which they want to use to persist whatever configuration they need to. Currently our configuration sub system only allows this pluggability with services. It probably needs to be extended to arbitrary entities.
It is up to you to choose, both have benefits. Since you are going to the trouble of building a UI, having an actual set of objects which you persist probably makes more sense, since this is how wicket works. However the extension points that you would need to this are not quite there, so it would take a bit of work on the core to enable this.
-Justin
Alan Gerber wrote:
Hi.
I'm working on the proxy module Dwins mentioned earlier. It will have a Wicket config UI, and will store configuration somewhere as well as access it during runtime.
What conventions are there for storing configuration information & accessing it during runtime?
Thanks,
Alan
------------------------------------------------------------------------------_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.