Hi Davis,
You are hitting on one of more untidy parts of geotools. The current feature api is a mess. I dont think its actually possible to create a feature type without using a deprecated method.
That being said, there is light at the end of the tunnel. The geotools feature model was recently redone, however its still on a development branch at the moment.
As for GeoServer, the code base will be moving to trunk after the 1.3.0 release which is scheduled for mid january. At this time we would like to merge Gabriels complex data store into the core which involves the new feature model.
Sorry for the babble, to answer your original question, we always try to maintain backwards compatibility, but in this case I am sure there will have to be a few breakages (Jody can correct me if I am wrong here). Lucky for GeoServer, most of the Feature interaction takes place through the DataStore api, which is quite stable. So I dont anticipate a huge amount of breakage when the move to the new feature model takes place. From what I remember you have implemented a custom data store so you may be less sheilded from the changes.
So I am not sure I actually answered your question, however Jody (or someone else more familiar with the new feature model) should be able to provide a bit more information about how your code will actually change with the new model.
-Justin
Davis Ford wrote:
Hi, some questions on current javadoc notes on the GeoTools website...
http://udig.refractions.net/docs/api-geotools/org/geotools/feature/FeatureType.html
...says the create methods are deprecated (for creating features from
the FeatureType interface). It says to use FeatureFactory instead,
but if I look at FeatureFactory interface..
http://udig.refractions.net/docs/api-geotools/org/geotools/feature/FeatureFactory.html
...it says the create methods here are deprecated as well b/c schema
information is required. I'm a bit confused. What is the proper way
to go about actually creating features?
Caveat -- is that I'm stuck with a dependency on GeoServer, and
GeoServer is currently only compatible with GeoTools 2.1.x. What is
the recommended way for me to proceed with creating features to be the
most forward-compatible with the next GeoTools when GeoServer supports
it?
Regards,
Davis
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Geotools-gt2-users mailing list
Geotools-gt2-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
--
Justin Deoliveira
The Open Planning Project
http://topp.openplans.org