A major goal for GeoServer 2.0 is to improve the web user interface. This will involve dropping the current STRUTS-based web administration tool in favor of one built on Wicket.
Aside from general usability, the new interface's chief advantage will be its pluggability. Plug-ins to GeoServer will define their own user interface, which will be picked up by the core. This makes non-core additions to GeoServer more viable. That will keep GeoServer's core tight while allowing the extendedsoftware to be more flexible overall.
There is a working prototype available for download: GeoServer 2.0.0-alpha1. But the prototype UI needs to be made bug free and user friendly before it can be included in GeoServer 2.0..
Funding
This roadmap item was funded by OpenGeo.
REST configuration was added to GeoServer 2.0 and is part of the OpenGeo Suite Community Edition and the OpenGeo Suite Enterprise Edition.
Get a quote now!
Get a quote or read more about core development to add your support to a road-map item.
Other Roadmap Items
Currently the layers that GeoServer publishes are the same for all users. We'd like to introduce the concept of “workspaces”, a logical collection of layers, optionally with limited security permissions, accessible from a unique end point.
Currently features are only accessible via the Web Feature Service (WFS) API. REST feature access will provide a ”resource oriented“ approach to accessing geographic collections. It will also use the existing AtomPub specification to provide for feature viewing and editing.
Funded: A new, cleaner user interface built on the Wicket web framework debuted with GeoServer 2.0