On Thu, Jan 23, 2014 at 12:44 AM, Justin Deoliveira <
jdeol...@boundlessgeo.com> wrote:
> Well the exception in this case seems to result from a call to
> Feature.getName(), which affair for simple features isn't ever used. And in
> the case of jdbc features we actually have a custom implementation based
> directly on a jdbc ResultSet.
>
> A few options here.
>
> 1. Implement getName() in ResultSetFeature and return null?
> 2. Ditch ResultSetFeature and use a normal feature that implements
> getName().
>
I was looking into the implementation of ResultSetFeature, it seems to me
many of these
methods throwing an unsupported operation exception do so without reason
(besides
avoiding the effort to implement them, that is ;-) )
For example in SimpleFeatureImpl getName() is simply
return featureType.getName();
and ResultSetFeature could do exactly the same.
The same goes for getAttributes() and a number of other methods.
If Carlo has time I'd go for improving the existing implementation of
ResultSetFeature to better
match SimpleFeatureImpl
Cheers
Andrea
--
== Our support, Your Success! Visit http://opensdi.geo-solutions.it for
more information ==
Ing. Andrea Aime
@geowolf
Technical Lead
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549
http://www.geo-solutions.it
http://twitter.com/geosolutions_it
-------------------------------------------------------
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
