Hi Jody,
I wasn't able this time, I will make up for it next time.
I have new PR for getCount() issue:
https://github.com/geotools/geotools/pull/1252
I also made a branch on my own repo with a community module that proves
backwards compatibility between wfsng and wfs from a geoserver point of
view.
I don't know if this is what @Andrea wanted and if it is sufficient.
I also don't know if it is worth committing this (and creating a new
module just for this little test) or the fact that I did it is enough:
https://github.com/NielsCharlier/geoserver/tree/wfsng
Regards
Niels
On 26-07-16 04:48, Jody Garnett wrote:
Thanks Niels, I picked up the other wgs-ng patch during the friday
sprint. I was sorry you did not join us as it would of been good to
collaborate on this.
I am going to start prepping the migration of AbstractDataStore to a
community module in anticipation of your success fixing wfs-ng.
--
Jody Garnett
On 25 July 2016 at 12:35, Niels Charlier <ni...@scitus.be
<mailto:ni...@scitus.be>> wrote:
Hi Jody,
I've added a patch for WFS2.0 in MapServer to the existing PR.
A couple more fixes are coming.
Regards
Niels
On 22-07-16 18:45, Jody Garnett wrote:
Thanks for the positive feedback, Niels has a couple of pull
requests ready and then we should be able to complete the
"migration" ... perhaps later today!
--
Jody Garnett
On 22 July 2016 at 09:12, Pierre Mauduit
<pierre.maud...@camptocamp.com
<mailto:pierre.maud...@camptocamp.com>> wrote:
Hi,
(perhaps due to lack of use).
FYI we stumbled upon several issues with the classic wfs
module in the geOrchestra extraction webapp (mainly related
to basic-authentication being dropped across requests, but we
are using a quite old geotools version too). We migrated to
wfs-ng in february, and it works way better in our case (we
might have had some weird behaviour with the WFS namespaces
though).
Regards,
-- Pierre
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity
planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
<mailto:GeoTools-Devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth
and traffic
patterns at an interface-level. Reveals which users, apps, and
protocols are
consuming the most bandwidth. Provides multi-vendor support for
NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using
capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
<mailto:GeoTools-Devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports.http://sdm.link/zohodev2dev
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
