Another angle to look at this is how deep the MapContext hierarchy really is.
> GeoServer uses a WMSMapContext which is a sub-sub-subclass of MapContext.
> What is going to happen to the other two subclasses of MapContext?
> (see attached picture, showing the inheritance hiearchy).
Thanks for the picture; my understanding is some of those subclasses allow for
things like watermarking;
it is my hope that by taking these facilities into MapContent that GeoServer
can accomplish the same goal without deep subclassing.
I should point out that the change to MapContent has been done; and the above
code is still working correctly. Is renderer subclassed as well?
I would like to know specifically what those two subclasses are up to; as they
represent a design requirement of some sort or other.
> I guess we'll have to suck up all the fields we need in GeoServer
> WMSMapContext and derive directly from MapContent to avoid deprecations?
That would be nice; the requirements of WMSMapContext could also drive this so
we can sort out what deprecations are needed.
Thanks for looking into this in greater detail Andrea,
Jody
------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network
management toolset available today. Delivers lowest initial
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd
_______________________________________________
Geotools-devel mailing list
Geotools-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
