(Appoligies to those who I've already inadvertantly spammed with the following on WFS-dev):
I'm seeking to implement a "transforming WFS adaptor", i.e. a service that sits between an external WFS client and server and allows custom transformations to be performed on the geometry (the specific transformations to be determined polymorphically). Internally, there are 3 adaptor components: the client (which connects to the external WFS server), the server (which connects to the external WFS client) and the transformer (which polymorphically transforms client output to server input). While I've achieved this using a weakly-typed API (i.e. XML as String) together with XSLT, it would clearly be preferable (from an adaptor developer's perspective) if the API had the explicit representation of features as Java objects that GeoTools offers. Any tactical advice on how this could best be achieved using existing GeoTools components (perhaps taking the WFSClient example from org.geotools.demo.example as a base?) would be greatly appreciated. Regards, Jerry. This message has been checked for viruses but the contents of an attachment may still contain software viruses, which could damage your computer system: you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
