On 16/08/10 11:18, Andrea Aime wrote:
> Luca Morandini ha scritto:
>>
>> I analysed the dependencies amongst classes, and the result were not truly
>> encouraging: for instance, there are about 867 classes depending on
>> WeakHashSet (a
>> lot of them within the catalog: LayerInfo, DataStoreInfo, etc, etc).
>
> Mumble... it's probably due to the fact we keep a
> CoordinateReferenceSystem object in some of them?
Indeed, but there may be other dependencies too.
> Does the tool show how you get to WeakHashSet from a certain class?
Yes.
> Do you have some examples
For instance: FeatureTypeInfoImpl has many paths leading to WeakHashSet, but
every
one of them go thru the CRS class (in turn leading to CanonicalSet and
WeakHashSet).
Same for StoreInfoImpl.
What about trying to replace the CanonicalSet class with something not using
WeakHashSet and see how the dependency tree is pruned ?
Regards,
--------------------
Luca Morandini
www.lucamorandini.it
--------------------
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
