Bug 968 - [Chameleon - Widget] WMSBrowser cannot recieve capabilities NOT Working
: [Chameleon - Widget] WMSBrowser cannot recieve capabilities NOT Working
Status: REOPENED
: Chameleon
AdminTools
: 2.0
: PC Windows XP
: P2 normal
: ---
Assigned To:
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2005-02-17 15:41 by
Modified: 2005-02-17 17:31 (History)


Attachments


Note

You need to log in before you can comment on or make changes to this bug.


Description From 2005-02-17 15:41:21
Chad, Jeff and I have not been able to connect to a single wms. No successful
connection, several 


One error I received on wms: 
http://wms.cits.rncan.gc.ca/cgi-bin/cubeserv.cgi? 

XPath error in xpath.class.php:436 XML error in given file
http___wms_cits_rncan_gc_ca_cgi_bin_cubeserv_cgi_.xml' on line 1 column 0.
Reason:not well-formed (invalid token)

I downloaded the capabilities document and xml validated it. I checked out
against the Schema:

<WMS_Capabilities version="1.1.3" xmlns="http://www.opengis.net/wms"
xmlns:xlink="http://www.w3.org/1999/xlink"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/wms
http://schemas.cubewerx.com/schemas/wms/1.1.3/WMS_Capabilities.xsd">

This issue may or may not be related to bug 965 ???

This is a major problem since it makes the widget useless.

It is important that this widget is fixed, since Carleton will be using it to
build ogc Context documents and search for wms services.
------- Comment #1 From 2005-02-17 16:16:56 -------
Chris,

this issue is not related to bug 965.

965 is about not being able to preview certain layers when the layers have a
certain type of nesting on the WMS.

Your problem is about not being able to add services, ie WMS capabilities
parsing problems.

Bart
------- Comment #2 From 2005-02-17 16:18:26 -------
I think this is the same problem as bug 962.  Please see that bug for a fix.
------- Comment #3 From 2005-02-17 17:14:46 -------
Thanks paul..... I will look into fixing bug 962

setting bug to invalid
------- Comment #4 From 2005-02-17 17:31:56 -------
Thinking about it I have decided to change my direction of this bug to the
Chameleon Admin. :) The issue actually lies in the fact that I (the user) did
not even now that the wmsparer was not registered correctly.

I was given no error on load of application or within the Chameleon Admin pages.

Couldn't an error be captured that makes sense when wms capabilities are been
registered to chameleon?