That Schema stuff from WMS is part of the old "XDO" xml parsing framework that is no longer supported; you will be making use of the GTXML framework (ie set up a configuration; create a parser with that configuration; and ask the parser to turn the http response into objects for you).
I thought this would be the case. I've got most of what you mention in place for my WCS implementation, just nothing for parsing the documents (I still can't generate code from the WCS schema!). In short there is not that much to learn about parsing from the WMS code (only how to organze your WCS implementation). You can however look at the WebFeatureServer 1.1 implementation for an example of parsing a capabilities document using GTXML; you will take similar steps when creating a WebCoverageService. I've been looking at the WFS code and it seems like I need something similar to the WFS_1_1_0_Protocol for each version of WCS, is this correct? As for bindings, could I steal ones which have already been generated (like from GeoServer) rather than generate my own? I also assume I can use the WCS 1.1 types found in net.opengis.wcs? Cheers, Jon -- View this message in context: http://n2.nabble.com/How-to-load-a-WCS-capabilities-document-tp2598821p2610022.html Sent from the geotools-gt2-users mailing list archive at Nabble.com. ------------------------------------------------------------------------------ This SF.net email is sponsored by: High Quality Requirements in a Collaborative Environment. Download a free trial of Rational Requirements Composer Now! http://p.sf.net/sfu/www-ibm-com _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
