Thanks all for the initial info and direction.

I have indeed tried just a quick WMS client with both 2.4.x and 2.5.x
branches, and just changing out the allows me to process a request and parse
through the capabilities document correctly. 

Jody, you are indeed correct that the program I have inherited does
significantly more than just WMS interactions. I have started looking into
upgrading to the newest 2.5.7 branch, but I do foresee a fair amount of work
in upgrading. The combination of the data model changing, and the gratuitous
use of hacks by the previous owners of the code base make it a daunting
task. 

As to the GTCloneUtils, I believe it was deprecated in the 2.4.x branch, but
still used for object cloning in our code base. I noticed that the
underlying objects in question do implement Cloneable, so I am unsure
whether or not I don't need to handle that or not anymore. I apologize for
being vague, but I haven't looked at that part of the code in a while. When
I get back to those errors again, I will be able to be more specific there.

At this point, I am trying to determine if the upgrade is really the best
path for the project, or if there might be a way to hack together something
to deal with the capabilities document that ESRI provides.

Thanks all for your insight and help,

~Moverton
-- 
View this message in context: 
http://n2.nabble.com/Re-geotools-dev-Geottols-WMS-connection-with-ESRI-Server-tp3607022p3612369.html
Sent from the geotools-gt2-users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with 
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users

Reply via email to