Message-ID: <1291060270.6813.1414186659359.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_6812_812714170.1414186659359" ------=_Part_6812_812714170.1414186659359 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This page outlines the current project to develop a WFS 1.1 capa= ble=20
We're going to develop a DataStore for WFS 1.1 servers. There is current=
ly a WFS DataStore though. The problem with it is it's fairly unmaintained =
and hard to maintain, is built upon deprecated XML/GML parsing technology, =
and works only for WFS 1.0 services.
By the other hand its a long liv= ed DataStore and thus has got a lot of bug fixes and per-server specific pa= tches (given than some WFS servers tend to have their own glitches)
S= o the obvious question is why a new one and not extending/fixing the curren= t one.
Rationale is we got a set of requirements that would make doin= g so a so deep change that's practically easier to start from scratch. Yet,= we'll try to leverage all the knowledge held on the old WFS DataStore as t= o alleviate the task of dealing with real world servers.
The following is the set of requirements that'll drive the DataStore des= ign.=20
The following are documentation pages for GeoTools tech it's worth to ke= ep in mind for this project:=20