The violation of the validity test is a clear violation of specs.
The getprint tag mean the violation.
This is sufficiente
Il 07/giu/2014 16:30 <redm...@qgis.org> ha scritto:

>  Issue #10489 has been updated by aperi2007 -.
>
>
> Hi.
>
> I confirm that the action described resolve the validity problem.
>
> I modify the code of qgis-server adding the prefix and the namespace and
> schemaLocation missed.
> Also I comment the code for GetStyle and GetPrint in the GetCapability
> response.
>
> And voila' the response now is VALID.
>
> For me is ok .
>
> Now we have our "qgis-server" compliant with ogc and inspire.
>
> :))
>
> Regards.
> ------------------------------
> Bug report #10489: QGIS Server getcapabilites response is not WMS
> compliant ! <http://hub.qgis.org/issues/10489>
>
>    - Author: aperi2007 -
>    - Status: Open
>    - Priority: Blocker
>    - Assigned to:
>    - Category:
>    - Target version:
>    - Platform:
>    - Platform version:
>    - Status info:
>    - Resolution:
>    - Patch supplied: No
>    - Affected version: 2.2.0
>    - Causes crash or corruption: No
>    - Tag:
>
> Hi,
>
> the response of the QGIS Server trunk version don't seem to be WMS
> Compliant.
>
> I tested it using XML Spy Enterprise and it response the GetLegendGraphics
> is put in wrong place.
>
> I try using this request:
>
>
> http://www502.regione.toscana.it/geoscopio_qg/cgi-bin/qgis_mapserv?map=continuum_geologico_rt.qgs&SERVICE=WMS&request=GetCapabilities&version=1.3.0
>
> Also I attach the image from my xmlspy with hard sentence.
>
> Perhaps there some setting to set QGIS to response a valid xml for OGC
> clients ?
>
> Thx.
> ------------------------------
>
> You have received this notification because you have either subscribed to
> it, or are involved in it.
> To change your notification preferences, please click here:
> http://hub.qgis.org/my/account
>
_______________________________________________
Qgis-developer mailing list
Qgis-developer@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/qgis-developer

Reply via email to