>
> The code was just a test case to read out data with the new wfs-ng module.
> You are right for this issue it is not realy necessary.
> I thought the recommended way to read out Data from a WFS is using a
> featureSource. As I understand the getSchema() call only returns the
> FeatureType (description of the FeatureType) and not the data itself. If
> there is a more perfomant way to get the data please enlighten me. :-)
>
> It is more that you should keep the featureSource around and use it "like
a session" for interacting with the data. Indeed you can configure it with
a Transaction object which will make it an independent sessions. For JDBC
DataStores the difference is more profound - the default of
Transaction.AUTO_COMMIT will grab a connection from the pool each time the
feature source is used. Creating your own transaction will allow the
feature source to reuse the same transaction. Calling transaction dispose
when done will return the connection to the pool.
Aside: Yes I know the WFS server is stateless - however our wfs client is
not. It uses the transaction to build up a large request when editing.
Transaction.commit() sends this batch of edits off.
------------------------------------------------------------------------------
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
_______________________________________________
GeoTools-GT2-Users mailing list
GeoTools-GT2-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
