Comments inline.
On 24/04/2010, at 8:34 PM, Thorsten Reitz wrote:
> Hi Jody,
>
> thanks for your response. This probably would mean significant reworking
> of the application, and I just have a few questions before doing so:
Sorry about that - you are on the "Cutting Edge" as it were; you may wish to
talk to Ben Cardadoc-Davies who heads up a team doing similar work on the app
schema plugin.
>
> - Is there a FeatureCollection for handling and filtering of FeatureImpl
> objects? Trying to store a FeatureImpl in a DefaultFeatureCollection
> throws a ClassCastException.
DefaultFeatureCollection I think is specific to SimpleFeature - let me check ..
yes it is.
Now I do see some of Ben's code that is not SimpleFeature specific:
- SampleDataAccessFeatureCollection
-MappingFeatureCollection
I also note that FilteringFeatureCollection is not SimpleFeature specific (it
uses generics to indicate what kind of features it is working with).
The filter api itself is not SimpleFeature specific; indeed it work work with
Feature, java.util.Map and Java Beans. The filter api uses expressions rather
then talk to content directly; and the Property expression that is used to look
up values can be taught about different kinds of content.
>
> - Can the Geotools StreamingRenderer also work with FeatureImpl objects?
Yes; it uses the same property accessor code and expressions as the filter
implementation.
>
> - Are there important differences in this regard (using FeatureImpl)
> between 2.5.8 (which I'm still using) and the current 2.6.2 release?
I cannot remember; I think the importance difference is the work of Ben's team
and as such I would expect the various things like rendering and xml generation
to be more tested in 2.6.x.
> Thanks again & kind regards,
Cheers,
Jody
------------------------------------------------------------------------------
_______________________________________________
Geotools-gt2-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
