org.vfny.geoserver.config

This class opperates as the Configuration Model and is stored in Web Container.

• Represents the Model of the STRUTS based Model-View-Controller Design
• Will support additional user-interface state, beyond requirements of the GeoServer application.
• Makes use of GeoTools2 Catalog/DataStore for FeatureType type names and FeatureType schema information/generation.
• To access live content, use the DataConfig.findDataStore()

Of the course of sorting this stuff out we have had a couple of bad ideas:

• It is tempting to replace a lot of these classes by changing the scope of the FormBeans to session, rather than request. I cannot convince my self that this would be a good idea, as storing the configuration model (and associated resources in the Web Container) is sure to prevent duplication in the face of multiple users configuring differnt subsystems. If the state was limited to session - they would manage to overwrite each other with no prior warning.
• It is tempting to make the Actions use the DTO objects directly (or forgo the config classes entierly). Having the config classes allows us to make whatever methods we need for easy, quick ui developement without breaking the rest of the application.

Represents most of a xs:element for an XMLSchema.

we have three types of information to store, Schema defined types, references and extentions on types.

Used to set-up config's memory model.

Represents the portion of a namespace required for the configuration of geoserver.

I made a real minor extension to the usual form of a JASC pal file which allows us to provide values in the #ffffff or 0Xffffff hex form.

Note that this kind of file does not support explicitly setting transparent pixel.

ServiceConfig is intended to be extended to provide some basic data storage facilities.