Front page capabilities link integration
----------------------------------------
Key: GEOS-4162
URL: http://jira.codehaus.org/browse/GEOS-4162
Project: GeoServer
Issue Type: Sub-task
Components: GWC, Wicket UI
Affects Versions: 2.1-beta1
Reporter: Gabriel Roldán
Assignee: Gabriel Roldán
Fix For: 2.1-beta2
Currently the only way to get to the GWC WMS-C capabilities document is by
being logged in or know the exact location.
Moreover, GWC provides additional services besides WMS-C. For instance: TMS and
WMTS.
The links to the capabilities docs for those services should be advertised in
the GeoServer front page as for the other services.
But, it is not that easy to fake the GWC service implementations as geoserver
ServiceInfo instances so that the front page catches them from the application
context and automatically creates GetCapabilities links for them, due to the
assumptions made in the page.
First thing coming to mind is an extension point that provides the actual
capabilities URL (since in the case of GWC services they even have a different
base: <context path>/gwc/service), and a default implementation that picks the
ServceInfo instances from the app context and does exactly what the front page
does now with them. But I'm open to suggestions.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
