Hello there:
As you can see, the OGC CITE compliance tests have been failing for the
last few days:
http://hudson.opengeo.org/hudson/view/cite/job/cite-wfs-1.1-master/761/.
The reason for that is a patch that was submitted for issue GEOS-4011:
https://github.com/geoserver/geoserver/pull/168
The problem here lies in the fact that the OGC and the W3C specifications
do not agree with each other. According to the OGC, the content type served
by GeoServer should be Content-Type: application/xml; subtype=gml/x.x.x,
while the W3C says that it should be Content-Type: application/xml;
subtype="gml/x.x.x"
So, given that GeoServer has a so called "Strict CITE compliance" mode,
whose value is used to establish the citeCompliant property of the
org.geoserver.ows.Dispatcher class, perhaps we could change its behaviour
so that it serves Content-Type: application/xml; subtype=gml/x.x.x when the
"Strict CITE compliance" mode is enabled and Content-Type: application/xml;
subtype="gml/x.x.x" when it is not. Therefore, the patch in question would
become something like this:
//check for SOAP request
if (req.isSOAP()) {
req.getHttpResponse().setContentType(SOAP_MIME);
}
else {
if (!citeCompliant) {
mimeType = mimeType.replaceAll("(subtype=)(gml/[0-9.]*)",
"$1\"$2\""); // fix for [GEOS-4011]
}
req.getHttpResponse().setContentType(mimeType);
}
Care to comment about this?
Best wishes.
--
ni hao ma?
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
