Hi Andreas, please open up a ticket, in gxp the same thing is done:
https://github.com/opengeo/gxp/blob/master/src/script/plugins/WMSSource.js Best regards, Bart > Hi, > > Speaking about the WMSCapabilitiesLoader: > It would be convenient if the responseXML structure would be accessible > for later processing. Currently, to my knowledge, responseXML is deleted > after processing - am I right? > > In my case I want to read out some vendor specific properties that are > not exposed by the WMSCapabilitiesLoader. Currently I extend the > WMSCapabilitiesLoader, overwrite the "ProcessResponse" method and expose > the XML structure. But I guess that I am not the only one that wants to > get access to the original XML structure of the WMSCapabilities? Maybe > the WMSCapabilities object could be extended to expose the original > structure for further processing? > > Should I open a ticket on this? > > Andreas > > On Tue, 25 Jan 2011 08:52:30 +0100, Eric Lemoine wrote: >> On Fri, Jan 21, 2011 at 7:49 PM, Alexandre Dube <[email protected]> >> wrote: >>> Hi, >>> >>>  While using the WMSCapabilitiesLoader, if a WMS GetCapabilities >>> request >>> returns an empty responseText or responseXML, the method that loads >>> the >>> 'capabilities' objet is called but doesn't check if it's populated >>> with >>> capability features. >>> >>>  The attached patch fixes the issue.  Is it worth opening a ticket ? >>>  If so, >>> please let me know and I'd do it and attach the patch. >> >> Please do. Thanks Alexandre. > > -- > -- > Andreas Neumann > Böschacherstrasse 10A > 8624 Grüt (Gossau ZH) > Switzerland > _______________________________________________ > Dev mailing list > [email protected] > http://www.geoext.org/cgi-bin/mailman/listinfo/dev > _______________________________________________ Dev mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/dev
