Thanks so much Andrea.
Just like to emphasize that we have verified that the bug does not appear
in v2.6.5 and started in v2.7.0. This might be helpful to know for the devs.
Regards.
On Thu, Nov 16, 2017 at 6:35 PM, Andrea Aime
wrote:
> Hi Mario, that's indeed
Hi Mario, that's indeed the first time I see the script... in any case,
I've attached it to the
ticket and verified that indeed it works.
The ticket is marked for attention in the monthly bug fix sprint, now
everything is ready
and we just have to wait for a dev to pick the ticket in one of the
Hello Andrea,
Are you referring to the test? I have included a short script that can
reproduce the problem and we have used that script on different versions of
GeoServer.
Anyway, will include it again here.
Thanks,
Mario.
On Thu, Nov 16, 2017 at 4:34 PM, Andrea Aime
Hi Mario,
see my last comment on the ticket and try to follow up please.
Cheers
Andrea
On Thu, Nov 16, 2017 at 8:14 AM, Mario Basa wrote:
> We are still experiencing the WFS bug described in
>
> https://osgeo-org.atlassian.net/browse/GEOS-7961
>
> with the following
We are still experiencing the WFS bug described in
https://osgeo-org.atlassian.net/browse/GEOS-7961
with the following versions of GeoServer:
- 2.7.1.1
- 2.10.2
- 2.12_20171108.
Below is a simple shell script to replicate the problem by doing a
BBOX getfeature request using epsg:900919 on