Arne Kepp wrote: > Justin Deoliveira wrote: >> Hi all, >> >> As part of recent hacking moving towards 2.0 i have been working on a >> new data directory for 2.x better suited to our configuration. Here is >> the proposal. Feedback welcome. >> >> http://geoserver.org/display/GEOS/GSIP+34+-+New+data+directory+structure+for+2.x >> >> -Justin > I thought we were going to cover up the distinction between coverage > store and data store ? If so, I think we should do the same in > directory structure and use subclassing as needed. We could do that yeah, instead of having coveragestore.xml and datastore.xml we could just make it store.xml. Not sure it gains us much , while the code reading the configuration might be made a bit simpler, it makes it harder to figure out what is what when you are looking at. Size in one, half dozen in the other i guess :). Anyone else have an opinion? > > How are modules / plugins expected to add to this configuration ? New > files in the directories, or do we provide some hooks to put it straight > into the XML files? If we do the latter, then core modules should use > these hooks too to ensure that they're actually usable and maintained. Good question. For things like new services it should be pretty straight forward, and there is already an extension point in place for doing so. Basically each service gets its own .xml file. For things like output formats, the metadata map of a service seems like a logical way to go. There is an extension point (GeoServerIntializer) in which modules can use to initialize themselves after configuration has been read. For new types of resources and entities in the catalog... it gets a bit tricky. While the catalog interfaces are written in a way to make them extensible, most of the code accessing them and persistence stuff does not assume that. So to be able to have pluggable resources some work would need to be done. How they are stored... i guess the same way data stores and coverages, feature types and coverages are stored.
> > -Arne > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
