Hi all,
at a deeper inspection on geoserver master (2.3-SNAPSHOT) it looks like the stuff works as espected.
In that case the WMS GetCapabilities 1.1.1 does not contain the element VendorSpecificCapabilities unless we enable GWC direct integration and specify tiled=true on the request.
Moreover in this second case we have an update GetCapabilities which prints on the header the following
<!DOCTYPE WMT_MS_Capabilities SYSTEM "[http://localhost:8080/geoserver/schemas/wms/1.1.1/WMS_MS_Capabilities.dtd](http://localhost:8080/geoserver/schemas/wms/1.1.1/WMS_MS_Capabilities.dtd)"[
]>
resulting in a valid document.
On the other side if we declare a VendorSpecificCapabilities element on the WMSCapabilities.DTD this will cause conflicts with the vendors’ one.
That means that at least on master branch there is no issue on the GetCapabilities.
Ing. Alessio Fabiani
@alfa7691
Founder/Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 331 6233686
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
On Tue, Aug 21, 2012 at 6:31 PM, Justin Deoliveira <jdeolive@anonymised.com> wrote:
I can;t of a reason off the top of my head why that would have been taken out… might have been an oversight. I guess i would start by going through history to find out what it changed. Any to be clear when you say trunk do you mean 2.2.x or master?
Also +1 for modifying the wms capabilities dtd to ensure it validates, etc…
On Tue, Aug 21, 2012 at 7:02 AM, Andrea Aime <andrea.aime@anonymised.com8…> wrote:
On Tue, Aug 21, 2012 at 3:54 PM, Alessio Fabiani <alessio.fabiani@anonymised.com> wrote:
Dear all,
while trying to understand why I’m having troubles with WMS GetCapabilities document using GeoServer 2.2.x, thanks to Andrea’s help we discovered that a fix done by Gabriel time ago is no longer available on branches.
I’m referring to this one https://fisheye.codehaus.org/changelog/geoserver/?cs=15227
which has a lot of sense. Without this fix the current WMS GetCapabilities document is not valid at all, because there is no declaration of the VendorSpecificCapabilities element on the standard OGC DTD.
Accordingly to the Gabriel’s fix, a vendor should contribute to the internal DTDs by specifying through an extension, it’s own VendorSpecificCapabilities element.
Any one has some ideas or suggestions? Who can take care of restoring the fix?
Btw, wondering, should we also add the VendorSpecificCapabilities element declaration in the DTD,
so that documents that do use the extensions, such as INSPIRE ones, are still opened properly with
Internet Explorer?
Cheers
Andrea
–
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
–
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Live Security Virtual Conference
Exclusive live event will cover all the ways today’s security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
Geoserver-devel mailing list
Geoserver-devel@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel