Message-ID: <541859762.5829.1369529001982.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_5828_1615851732.1369529001982" ------=_Part_5828_1615851732.1369529001982 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
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 lived DataStore and thus has got a lot of bug = fixes and per-server specific patches (given than some WFS servers tend to = have their own glitches)
So the obvious question is why a new one and not extending/fixing the curre= nt one.
Rationale is we got a set of requirements that would make doing so a so dee= p 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 to alleviate t= he task of dealing with real world servers.
The following is the set of requirements that'll drive the DataStore des= ign.
The following are documentation pages for GeoTools tech it's worth to ke= ep in mind for this project:
WFS GML DataStore
Current WFS DataStore issues: 58 issues
Andrea's brain dump<= br /> Christophe Google Summe= r of Code project
XML Developers Guide