org.vfny.geoserver.config.package.html Maven / Gradle / Ivy
GeoServer Config package
Configuration Model being edited.
This class opperates as the Configuration Model and is stored in Web Container.
Details:
-
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.