[eoxserver-dev] GetCapabilites: ServiceMetaData version attribute does not validate

[Novacek, Milan]

Hi Fabian,
 I guess it could be picking up a bogus mapscript module somewhere.
In any case with mapserver r12549 and the correct MAPSCRIPT_PATH it works fine - I now get the correct ServiceMetaData element.

Thanks Fabian and Stephan.

Milan Novacek 



-----Original Message-----
From: dev-bounces at eoxserver.org on behalf of Fabian Schindler
Sent: Tue 10/4/2011 9:21 AM
To: dev at eoxserver.org
Subject: Re: [eoxserver-dev] GetCapabilites: ServiceMetaData version attribute does not validate
 
Milan,

The MAPSCRIPT_PATH option should direct to 
'mapserver/mapserver/mapscript/python/build'. It is just a shorthand for 
what could be achieved with the environment variable PYTHONPATH, a path 
to include additional python modules.

Is it possible that you have another mapscript version installed? Maybe 
an older mapserver package from your OS package repository? It might be 
the case that this module is loaded instead of the one MAPSCRIPT_PATH is 
pointing to.

Fabian Schindler



On 10/04/2011 09:11 AM, Novacek, Milan wrote:
> Stephan,
>    Question about MAPSCRIPT_PATH - should it point to the  mapserver/mapscript directory, or to 'mapserver/mapscript/python/build' ?
>
>    There is a MAPSCRIPT_PATH issue in any case: if I point it to a non-existent directory (e.g. '/home/foo'), then eoxserver runs, does not report anything wrong to the logfile, but incorrectly outputs the ServiceMetadata element with the version attribute.  It occurred to me that I might have a different 'settings.py' somewhere that eoxserver might be finding instead, but that is definitely not the case:  if I remove the settings.py file then exoserver does not run at all.
>
>
> Milan Novacek
>
>
>
> -----Original Message-----
> From: dev-bounces at eoxserver.org on behalf of Stephan Meißl
> Sent: Mon 10/3/2011 6:31 PM
> To: EOxServer Development Discussions
> Subject: Re: [eoxserver-dev] GetCapabilites: ServiceMetaData version attribute does not validate
>
> Milan,
>
> that's strange, EOxServer doesn't touch this part of the response.
> However, I just found out that there's a problem with the latest trunk
> of MapServer. We are going to fix this tomorrow. Meanwhile please use
> r12549 of MapServer (r12550 introduced the problem).
>
> Could you please check if you use the right version of MapServer from
> EOxServer (configured in settings.py with "MAPSCRIPT_PATH").
>
> cu
> Stephan
>
>
> On Mon, 2011-10-03 at 15:55 +0200, Novacek, Milan wrote:
>> Stephan,
>>    but this is originating from eoxserver, not mapserver.  Mapserver is fine; no extra version attribute there.
>> I think I'm running today's trunk version of eoxserver.
>>
>> Milan Novacek
>>
>>
>>
>> -----Original Message-----
>> From: dev-bounces at eoxserver.org on behalf of Stephan Meißl
>> Sent: Mon 10/3/2011 2:52 PM
>> To: EOxServer Development Discussions
>> Subject: Re: [eoxserver-dev] GetCapabilites: ServiceMetaData version attribute does not validate
>>
>> Hi Milan,
>>
>> I'm afraid there's something misconfigured as I'm pretty sure that I
>> changed the behavior 7 weeks ago in MapServer (see [1]) to not include
>> the version attribute.
>>
>> cu
>> Stephan
>>
>> [1] http://trac.osgeo.org/mapserver/changeset/12059
>>
>>
>> On Mon, 2011-10-03 at 14:01 +0200, Novacek, Milan wrote:
>>> Hi Stephan,
>>> I've updated to today'd snapshot of mapserver trunk.
>>> It outputs ServiceMetadata with the version number:
>>>    <wcs:ServiceMetadata version="1.0.0"/>
>>>
>>> Is this right?  If not, then I have something misconfigured and have to chase down why I'm picking up an old version somewhere.
>>>
>>> If it is right, then I don't see a wcs:ServiceMetadata with a version option in the schemas I have.
>>> I think I have the latest eoxserver trunk with the schemas.
>>>
>>>
>>> Milan Novacek
>>>
>>>
>>> -----Original Message-----
>>> From: dev-bounces at eoxserver.org on behalf of Stephan Meißl
>>> Sent: Mon 10/3/2011 12:12 PM
>>> To: EOxServer Development Discussions
>>> Subject: Re: [eoxserver-dev] GetCapabilites: ServiceMetaData version attribute does not validate
>>>
>>> Hi Milan,
>>>
>>> the definition of the 'ServiceMetadata' changed/will change in WCS 2.0.1
>>> and the schemas at eoxserver.org as well as the trunk of MapServer
>>> reflect this change already. Which version of MapServer are you running?
>>> I propose to compile the latest trunk.
>>>
>>> Best regards,
>>> Stephan
>>>
>>>
>>> On Mon, 2011-10-03 at 11:27 +0200, Novacek, Milan wrote:
>>>> Hi dev,
>>>>   I have problem validating the GetCapabilities response - in particular the 'version' attribute in the 'ServiceMetadata' element.
>>>> I guess I must be missing a schema definition for this.  After all it is in many of the examples.
>>>>
>>>>
>>>> Milan Novacek
>>>>
>>>>
>>>
>>>
>>
>>
>
>
>
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 5208 bytes
Desc: not available
URL: <http://eoxserver.org/pipermail/dev/attachments/20111004/76c202eb/attachment-0001.bin>