On Sat, Oct 12, 2013 at 11:16 AM, Justin Deoliveira <
jdeol...@boundlessgeo.com> wrote:
>
>
>
> On Sat, Oct 12, 2013 at 3:24 AM, Andrea Aime > wrote:
>
>> On Fri, Oct 11, 2013 at 11:46 PM, Ian Schneider <
>> ischnei...@boundlessgeo.com> wrote:
>>
>>> The complete death of the WfsDispatcher here:
On Sat, Oct 12, 2013 at 3:24 AM, Andrea Aime
wrote:
> On Fri, Oct 11, 2013 at 11:46 PM, Ian Schneider <
> ischnei...@boundlessgeo.com> wrote:
>
>> The complete death of the WfsDispatcher here:
>> https://github.com/geoserver/geoserver/pull/356
>>
>
> Hi Ian,
> the patch looks good to me, those com
On Fri, Oct 11, 2013 at 11:46 PM, Ian Schneider wrote:
> The complete death of the WfsDispatcher here:
> https://github.com/geoserver/geoserver/pull/356
>
Hi Ian,
the patch looks good to me, those comments about supporting WfsDispatcher
are as old as GeoServer 1.4.0,
so I believe it's high time
The complete death of the WfsDispatcher here:
https://github.com/geoserver/geoserver/pull/356
Do you reckon it would be okay to cherry-pick to 2.3.x, too?
On Fri, Oct 11, 2013 at 11:34 AM, Andrea Aime
wrote:
> On Fri, Oct 11, 2013 at 6:11 PM, Ian Schneider <
> ischnei...@boundlessgeo.com> wrote
On Fri, Oct 11, 2013 at 6:11 PM, Ian Schneider
wrote:
> The ticket outlines the issue in more depth but the crux of the problem is
> that DescribeLayer returns URLs with 'WfsDispatcher' on the end, something
> like: http://localhost:8080/geoserver/tiger/poi/wfs/WfsDispatcher?
>
> These URLs are no
The ticket outlines the issue in more depth but the crux of the problem is
that DescribeLayer returns URLs with 'WfsDispatcher' on the end, something
like: http://localhost:8080/geoserver/tiger/poi/wfs/WfsDispatcher?
These URLs are not usable as an exception occurs noting that the service
can't be
