Thanks.
Also I made a mistake with the schedule. April is a potential 1.6 release,
mid May is the first window for a new 1.7 release. An earlier release
would only be for critical bug fixes.
On 23 March 2015 at 14:07, xavier lhomme <lhomme.xavier@...> wrote:
> Hi ok I submitted issue #318. It will be the occasion to to work on #297
> and closed #222.
> But It will takes some time. I can only work at nigth...
> xl
>
> 2015-03-23 21:48 GMT+01:00 Kevin Smith <ksmith@...>:
>
>> Yes, that would be a good start. An even better one would be to create an
>> improvement ticket in the bug tracker, then make the pull request. If we do
>> backport it, 1.7.1 would be scheduled to go out in mid April.
>>
>> Since you seem to be our current expert on the topic of ArcGIS Cache, you
>> might want to take a look at another PR regarding the ArcGIS Cache support
>> https://github.com/GeoWebCache/geowebcache/pull/310 There's some
>> uncertainty whether the behaviour in question is something that varies
>> between ArcGIS caches and therefor need to be configurable, or if the
>> current behaviour in GWC is just wrong. Any input would be welcome. At
>> the moment I'm holding off on merging it until it's made configurable and
>> unit tests are added.
>>
>>
>>
>> On 23 March 2015 at 12:46, xavier lhomme <lhomme.xavier@...> wrote:
>>
>>> Hi kevin and community
>>>
>>> I agree that it's not a regression !
>>>
>>> Is it possible to produce a 1.7.1 version with the ArcGIS Cache (compact
>>> or exploded) compliant with the ArcGIS Server 10.1 or above ?
>>> Then with the "ximex" code ? that we can find here
>>> https://github.com/GeoWebCache/geowebcache/pull/223
>>> Note that in the "Geowebcache-users Digest, Vol 80, Issue 5" mail from
>>> the beginning of the month Ole Kofoed Pedersen had the same issue. then
>>> it's really a need.
>>>
>>> Do you want that I create a Pull Request in the master branch with the
>>> ximex code ?
>>>
>>> 2015-03-23 20:01 GMT+01:00 Kevin Smith <ksmith@...>:
>>>
>>>> Hi Xavier,
>>>>
>>>> It looks to me like you may have been using a patched custom build of
>>>> GWC since I can't find any sign of SpatialReference.LatestWKID in any of
>>>> the 1.6.x, 1.7.x, or master. SpatialReference hasn't been touched on any
>>>> of those branches since the initial commit.
>>>>
>>>> The revert was because ximax had submitted the PR against the 1.5.x
>>>> branch. I hadn't noticed that it wasn't going into master and merged it,
>>>> then reverted to correct my mistake. I think I emailed ximax to ask
>>>> for a revised PR to master (At least that's what I should have done).
>>>> Doing it that way is important in order to avoid precisely the sort of
>>>> regression where a new version lacks a previously introduced feature.
>>>> Since it was only ever on the 1.5.x branch, it had no effect on 1.6.x or
>>>> 1.7.x.
>>>>
>>>> Could you download a new 1.6 WAR from SourceForge and try that? I
>>>> think the error will still occur, indicating that this is not a regression
>>>> in the community codebase but rather a patch you applied to your instance.
>>>>
>>>> On 21 March 2015 at 06:45, xavier lhomme <lhomme.xavier@...>
>>>> wrote:
>>>>
>>>>> Hi kevin
>>>>>
>>>>> I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
>>>>> Server >= 10.1)
>>>>> With ArcGIS 10.1 or above some parameters have been added in the
>>>>> conf.xml file like LatestWKID ...
>>>>>
>>>>> ximax has proposed in "Commits on Jan 29, 2014" a patch which you
>>>>> merge first. #223
>>>>> But you revert this merge on 15 Jul 2014
>>>>>
>>>>> Perhaps you do this to ensure backward compatibility with
>>>>> configuration file from ArcGIS 10.0 or 9.3 ?
>>>>>
>>>>> Is it possible to produce a 1.7.1 version with this patch ?
>>>>>
>>>>> xav
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> Kevin Smith
>>>>
>>>> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>>>>
>>>> ksmith@...
>>>>
>>>> +1-778-785-7459
>>>>
>>>> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>>>>
>>>>
>>>> <http://twitter.com/boundlessgeo/&gt;
>>>>
>>>> [image: http://boundlessgeo.com/]
>>>> <http://boundlessgeo.com/&gt;
>>>>
>>>
>>>
>>
>>
>> --
>>
>> Kevin Smith
>>
>> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>>
>> ksmith@...
>>
>> +1-778-785-7459
>>
>> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>>
>>
>> <http://twitter.com/boundlessgeo/&gt;
>>
>> [image: http://boundlessgeo.com/]
>> <http://boundlessgeo.com/&gt;
>>
>
>
--
Kevin Smith
Software Engineer | Boundless <http://boundlessgeo.com/&gt;
ksmith@...
+1-778-785-7459
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;
<http://twitter.com/boundlessgeo/&gt;
[image: http://boundlessgeo.com/]
<http://boundlessgeo.com/&gt;

Hi ok I submitted issue #318. It will be the occasion to to work on #297
and closed #222.
But It will takes some time. I can only work at nigth...
xl
2015-03-23 21:48 GMT+01:00 Kevin Smith <ksmith@...>:
> Yes, that would be a good start. An even better one would be to create an
> improvement ticket in the bug tracker, then make the pull request. If we do
> backport it, 1.7.1 would be scheduled to go out in mid April.
>
> Since you seem to be our current expert on the topic of ArcGIS Cache, you
> might want to take a look at another PR regarding the ArcGIS Cache support
> https://github.com/GeoWebCache/geowebcache/pull/310 There's some
> uncertainty whether the behaviour in question is something that varies
> between ArcGIS caches and therefor need to be configurable, or if the
> current behaviour in GWC is just wrong. Any input would be welcome. At
> the moment I'm holding off on merging it until it's made configurable and
> unit tests are added.
>
>
>
> On 23 March 2015 at 12:46, xavier lhomme <lhomme.xavier@...> wrote:
>
>> Hi kevin and community
>>
>> I agree that it's not a regression !
>>
>> Is it possible to produce a 1.7.1 version with the ArcGIS Cache (compact
>> or exploded) compliant with the ArcGIS Server 10.1 or above ?
>> Then with the "ximex" code ? that we can find here
>> https://github.com/GeoWebCache/geowebcache/pull/223
>> Note that in the "Geowebcache-users Digest, Vol 80, Issue 5" mail from
>> the beginning of the month Ole Kofoed Pedersen had the same issue. then
>> it's really a need.
>>
>> Do you want that I create a Pull Request in the master branch with the
>> ximex code ?
>>
>> 2015-03-23 20:01 GMT+01:00 Kevin Smith <ksmith@...>:
>>
>>> Hi Xavier,
>>>
>>> It looks to me like you may have been using a patched custom build of
>>> GWC since I can't find any sign of SpatialReference.LatestWKID in any of
>>> the 1.6.x, 1.7.x, or master. SpatialReference hasn't been touched on any
>>> of those branches since the initial commit.
>>>
>>> The revert was because ximax had submitted the PR against the 1.5.x
>>> branch. I hadn't noticed that it wasn't going into master and merged it,
>>> then reverted to correct my mistake. I think I emailed ximax to ask
>>> for a revised PR to master (At least that's what I should have done).
>>> Doing it that way is important in order to avoid precisely the sort of
>>> regression where a new version lacks a previously introduced feature.
>>> Since it was only ever on the 1.5.x branch, it had no effect on 1.6.x or
>>> 1.7.x.
>>>
>>> Could you download a new 1.6 WAR from SourceForge and try that? I think
>>> the error will still occur, indicating that this is not a regression in the
>>> community codebase but rather a patch you applied to your instance.
>>>
>>> On 21 March 2015 at 06:45, xavier lhomme <lhomme.xavier@...>
>>> wrote:
>>>
>>>> Hi kevin
>>>>
>>>> I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
>>>> Server >= 10.1)
>>>> With ArcGIS 10.1 or above some parameters have been added in the
>>>> conf.xml file like LatestWKID ...
>>>>
>>>> ximax has proposed in "Commits on Jan 29, 2014" a patch which you merge
>>>> first. #223
>>>> But you revert this merge on 15 Jul 2014
>>>>
>>>> Perhaps you do this to ensure backward compatibility with configuration
>>>> file from ArcGIS 10.0 or 9.3 ?
>>>>
>>>> Is it possible to produce a 1.7.1 version with this patch ?
>>>>
>>>> xav
>>>>
>>>
>>>
>>>
>>> --
>>>
>>> Kevin Smith
>>>
>>> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>>>
>>> ksmith@...
>>>
>>> +1-778-785-7459
>>>
>>> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>>>
>>>
>>> <http://twitter.com/boundlessgeo/&gt;
>>>
>>> [image: http://boundlessgeo.com/]
>>> <http://boundlessgeo.com/&gt;
>>>
>>
>>
>
>
> --
>
> Kevin Smith
>
> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>
> ksmith@...
>
> +1-778-785-7459
>
> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>
>
> <http://twitter.com/boundlessgeo/&gt;
>
> [image: http://boundlessgeo.com/]
> <http://boundlessgeo.com/&gt;
>

Yes, that would be a good start. An even better one would be to create an
improvement ticket in the bug tracker, then make the pull request. If we do
backport it, 1.7.1 would be scheduled to go out in mid April.
Since you seem to be our current expert on the topic of ArcGIS Cache, you
might want to take a look at another PR regarding the ArcGIS Cache support
https://github.com/GeoWebCache/geowebcache/pull/310 There's some
uncertainty whether the behaviour in question is something that varies
between ArcGIS caches and therefor need to be configurable, or if the
current behaviour in GWC is just wrong. Any input would be welcome. At
the moment I'm holding off on merging it until it's made configurable and
unit tests are added.
On 23 March 2015 at 12:46, xavier lhomme <lhomme.xavier@...> wrote:
> Hi kevin and community
>
> I agree that it's not a regression !
>
> Is it possible to produce a 1.7.1 version with the ArcGIS Cache (compact
> or exploded) compliant with the ArcGIS Server 10.1 or above ?
> Then with the "ximex" code ? that we can find here
> https://github.com/GeoWebCache/geowebcache/pull/223
> Note that in the "Geowebcache-users Digest, Vol 80, Issue 5" mail from the
> beginning of the month Ole Kofoed Pedersen had the same issue. then it's
> really a need.
>
> Do you want that I create a Pull Request in the master branch with the
> ximex code ?
>
> 2015-03-23 20:01 GMT+01:00 Kevin Smith <ksmith@...>:
>
>> Hi Xavier,
>>
>> It looks to me like you may have been using a patched custom build of GWC
>> since I can't find any sign of SpatialReference.LatestWKID in any of the
>> 1.6.x, 1.7.x, or master. SpatialReference hasn't been touched on any of
>> those branches since the initial commit.
>>
>> The revert was because ximax had submitted the PR against the 1.5.x
>> branch. I hadn't noticed that it wasn't going into master and merged it,
>> then reverted to correct my mistake. I think I emailed ximax to ask for
>> a revised PR to master (At least that's what I should have done). Doing it
>> that way is important in order to avoid precisely the sort of regression
>> where a new version lacks a previously introduced feature. Since it was
>> only ever on the 1.5.x branch, it had no effect on 1.6.x or 1.7.x.
>>
>> Could you download a new 1.6 WAR from SourceForge and try that? I think
>> the error will still occur, indicating that this is not a regression in the
>> community codebase but rather a patch you applied to your instance.
>>
>> On 21 March 2015 at 06:45, xavier lhomme <lhomme.xavier@...> wrote:
>>
>>> Hi kevin
>>>
>>> I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
>>> Server >= 10.1)
>>> With ArcGIS 10.1 or above some parameters have been added in the
>>> conf.xml file like LatestWKID ...
>>>
>>> ximax has proposed in "Commits on Jan 29, 2014" a patch which you merge
>>> first. #223
>>> But you revert this merge on 15 Jul 2014
>>>
>>> Perhaps you do this to ensure backward compatibility with configuration
>>> file from ArcGIS 10.0 or 9.3 ?
>>>
>>> Is it possible to produce a 1.7.1 version with this patch ?
>>>
>>> xav
>>>
>>
>>
>>
>> --
>>
>> Kevin Smith
>>
>> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>>
>> ksmith@...
>>
>> +1-778-785-7459
>>
>> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>>
>>
>> <http://twitter.com/boundlessgeo/&gt;
>>
>> [image: http://boundlessgeo.com/]
>> <http://boundlessgeo.com/&gt;
>>
>
>
--
Kevin Smith
Software Engineer | Boundless <http://boundlessgeo.com/&gt;
ksmith@...
+1-778-785-7459
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;
<http://twitter.com/boundlessgeo/&gt;
[image: http://boundlessgeo.com/]
<http://boundlessgeo.com/&gt;

Hi kevin and community
I agree that it's not a regression !
Is it possible to produce a 1.7.1 version with the ArcGIS Cache (compact or
exploded) compliant with the ArcGIS Server 10.1 or above ?
Then with the "ximex" code ? that we can find here
https://github.com/GeoWebCache/geowebcache/pull/223
Note that in the "Geowebcache-users Digest, Vol 80, Issue 5" mail from the
beginning of the month Ole Kofoed Pedersen had the same issue. then it's
really a need.
Do you want that I create a Pull Request in the master branch with the
ximex code ?
2015-03-23 20:01 GMT+01:00 Kevin Smith <ksmith@...>:
> Hi Xavier,
>
> It looks to me like you may have been using a patched custom build of GWC
> since I can't find any sign of SpatialReference.LatestWKID in any of the
> 1.6.x, 1.7.x, or master. SpatialReference hasn't been touched on any of
> those branches since the initial commit.
>
> The revert was because ximax had submitted the PR against the 1.5.x
> branch. I hadn't noticed that it wasn't going into master and merged it,
> then reverted to correct my mistake. I think I emailed ximax to ask for
> a revised PR to master (At least that's what I should have done). Doing it
> that way is important in order to avoid precisely the sort of regression
> where a new version lacks a previously introduced feature. Since it was
> only ever on the 1.5.x branch, it had no effect on 1.6.x or 1.7.x.
>
> Could you download a new 1.6 WAR from SourceForge and try that? I think
> the error will still occur, indicating that this is not a regression in the
> community codebase but rather a patch you applied to your instance.
>
> On 21 March 2015 at 06:45, xavier lhomme <lhomme.xavier@...> wrote:
>
>> Hi kevin
>>
>> I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
>> Server >= 10.1)
>> With ArcGIS 10.1 or above some parameters have been added in the conf.xml
>> file like LatestWKID ...
>>
>> ximax has proposed in "Commits on Jan 29, 2014" a patch which you merge
>> first. #223
>> But you revert this merge on 15 Jul 2014
>>
>> Perhaps you do this to ensure backward compatibility with configuration
>> file from ArcGIS 10.0 or 9.3 ?
>>
>> Is it possible to produce a 1.7.1 version with this patch ?
>>
>> xav
>>
>
>
>
> --
>
> Kevin Smith
>
> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>
> ksmith@...
>
> +1-778-785-7459
>
> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>
>
> <http://twitter.com/boundlessgeo/&gt;
>
> [image: http://boundlessgeo.com/]
> <http://boundlessgeo.com/&gt;
>

If you have a backup of your previous deployment, you could also compare
the gwc-arcgiscache jar files. You can find the jars for all recent
releases here
http://repo.boundlessgeo.com/main/org/geowebcache/gwc-arcgiscache/
On 23 March 2015 at 12:01, Kevin Smith <ksmith@...> wrote:
> Hi Xavier,
>
> It looks to me like you may have been using a patched custom build of GWC
> since I can't find any sign of SpatialReference.LatestWKID in any of the
> 1.6.x, 1.7.x, or master. SpatialReference hasn't been touched on any of
> those branches since the initial commit.
>
> The revert was because ximax had submitted the PR against the 1.5.x
> branch. I hadn't noticed that it wasn't going into master and merged it,
> then reverted to correct my mistake. I think I emailed ximax to ask for
> a revised PR to master (At least that's what I should have done). Doing it
> that way is important in order to avoid precisely the sort of regression
> where a new version lacks a previously introduced feature. Since it was
> only ever on the 1.5.x branch, it had no effect on 1.6.x or 1.7.x.
>
> Could you download a new 1.6 WAR from SourceForge and try that? I think
> the error will still occur, indicating that this is not a regression in the
> community codebase but rather a patch you applied to your instance.
>
> On 21 March 2015 at 06:45, xavier lhomme <lhomme.xavier@...> wrote:
>
>> Hi kevin
>>
>> I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
>> Server >= 10.1)
>> With ArcGIS 10.1 or above some parameters have been added in the conf.xml
>> file like LatestWKID ...
>>
>> ximax has proposed in "Commits on Jan 29, 2014" a patch which you merge
>> first. #223
>> But you revert this merge on 15 Jul 2014
>>
>> Perhaps you do this to ensure backward compatibility with configuration
>> file from ArcGIS 10.0 or 9.3 ?
>>
>> Is it possible to produce a 1.7.1 version with this patch ?
>>
>> xav
>>
>
>
>
> --
>
> Kevin Smith
>
> Software Engineer | Boundless <http://boundlessgeo.com/&gt;
>
> ksmith@...
>
> +1-778-785-7459
>
> @boundlessgeo <http://twitter.com/boundlessgeo/&gt;
>
>
> <http://twitter.com/boundlessgeo/&gt;
>
> [image: http://boundlessgeo.com/]
> <http://boundlessgeo.com/&gt;
>
--
Kevin Smith
Software Engineer | Boundless <http://boundlessgeo.com/&gt;
ksmith@...
+1-778-785-7459
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;
<http://twitter.com/boundlessgeo/&gt;
[image: http://boundlessgeo.com/]
<http://boundlessgeo.com/&gt;

Hi Xavier,
It looks to me like you may have been using a patched custom build of GWC
since I can't find any sign of SpatialReference.LatestWKID in any of the
1.6.x, 1.7.x, or master. SpatialReference hasn't been touched on any of
those branches since the initial commit.
The revert was because ximax had submitted the PR against the 1.5.x
branch. I hadn't noticed that it wasn't going into master and merged it,
then reverted to correct my mistake. I think I emailed ximax to ask for a
revised PR to master (At least that's what I should have done). Doing it
that way is important in order to avoid precisely the sort of regression
where a new version lacks a previously introduced feature. Since it was
only ever on the 1.5.x branch, it had no effect on 1.6.x or 1.7.x.
Could you download a new 1.6 WAR from SourceForge and try that? I think
the error will still occur, indicating that this is not a regression in the
community codebase but rather a patch you applied to your instance.
On 21 March 2015 at 06:45, xavier lhomme <lhomme.xavier@...> wrote:
> Hi kevin
>
> I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
> Server >= 10.1)
> With ArcGIS 10.1 or above some parameters have been added in the conf.xml
> file like LatestWKID ...
>
> ximax has proposed in "Commits on Jan 29, 2014" a patch which you merge
> first. #223
> But you revert this merge on 15 Jul 2014
>
> Perhaps you do this to ensure backward compatibility with configuration
> file from ArcGIS 10.0 or 9.3 ?
>
> Is it possible to produce a 1.7.1 version with this patch ?
>
> xav
>
--
Kevin Smith
Software Engineer | Boundless <http://boundlessgeo.com/&gt;
ksmith@...
+1-778-785-7459
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;
<http://twitter.com/boundlessgeo/&gt;
[image: http://boundlessgeo.com/]
<http://boundlessgeo.com/&gt;

Hi kevin
I'm using ArcGIS Compact Cache with GeoWebCache (generated with ArcGIS
Server >= 10.1)
With ArcGIS 10.1 or above some parameters have been added in the conf.xml
file like LatestWKID ...
ximax has proposed in "Commits on Jan 29, 2014" a patch which you merge
first. #223
But you revert this merge on 15 Jul 2014
Perhaps you do this to ensure backward compatibility with configuration
file from ArcGIS 10.0 or 9.3 ?
Is it possible to produce a 1.7.1 version with this patch ?
xav

I'm curious about the state of vector tiles, but I am left with more
questions than answers after looking at that link.
Is it http://openlayers.org/en/v3.3.0/examples/tile-vector.html , and is
anyone but Mapnik (or ESRI) able to generate these now ?
The tile format is a piece of cake, the work that would probably have to
be done is related to the framework in which they are used (the
equivalent of getcapabilities, error handling etc.). At first glance it
looks like Varnish and TMS in the example above.
-Arne
On 20/03/15 08:55 , xavier lhomme wrote:
> Hi,
>
> Is there any plans to support Vector Map Tiling conforming to the
> MapBox spécification (which seems to be supported to by ESRI too) ?
> See https://github.com/mapbox/vector-tile-spec
>
> XL
>

Hi all,
I'm building GeoServer on a machine where I didn't build it in the latest
months.
The build is stuck since it is unable to download geowebache artifacts from
there:
http://repository.codehaus.org/org/geowebcache ...
Should we consider removing the codehaus repository from the main pom or is
it used for some other artifacts?
Regards,
Nicola Lagomarsini.
--
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/NWWaa2 for more information.
==
Ing. Nicola Lagomarsini
Junior Software Engineer
GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
http://www.geo-solutions.ithttp://twitter.com/geosolutions_it
-------------------------------------------------------
*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.
The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

Yes my plan was ultimately to hide the Workspace parameter and have the
filter added and updated automatically the way the style filter is so it
would all be transparent to the user. I don't think you're missing
anything, I just wanted to make sure workspace renames were covered.
On 2 February 2015 at 12:44, Andrea Aime <andrea.aime@...>
wrote:
> On Mon, Feb 2, 2015 at 8:31 PM, Kevin Smith <ksmith@...>
> wrote:
>
>> I was looking at the same two problems in a different way. I'd
>> considered the prefix route on styles but hadn't noticed that solution to
>> the LayerGroups issue and wanted to solve both. So I ended up working on
>> improving the workspace parameter filter option instead, which lead to some
>> improvements in GWC I'm still working on, specifically GWC ticket #170.
>> The work I did should still be able to simplify the Style filter and make
>> it more robust, while also making other new parameter filters with
>> similarly dynamic behaviour easier to write and generally helping to avoid
>> 'leaking' of parameterized tile caches, particular when using the RexExp
>> filter.
>>
>> I don't think my route would have been backportable, and would have been
>> a stretch to make it into GWC 1.7.x/GS 2.7.x now that we are beta so, even
>> though it sort of obsoletes what I've been working on for the past few
>> days, I'm glad to see this.
>>
>
> I did not try to make the work backportable either (not with that
> intention at least), but I find the workspace parameter... ugh....
> GWC integration must be transparent, it's the primary feature of the
> integrated GW, a solution that breaks it is imho no solution, but a
> temporary band-aid in
> user's face (e.g., exactly where it should not be, band aids are ugly, but
> if needs be, better hide them under the carpet).
>
Yes my plan was ultimately to hide the Workspace parameter and have the
filter added and updated automatically the way the style filter is so it
would all be transparent to the user. The backportability issues I had
with my solution were that it involved API changes in GWC:
BlobStoreListener ended up with a new event to handle parameterizations
being purged. I wasn't happy with either of trying to put it in 1.7 this
late or waiting for 1.8. Since your solution is much less intrusive and
confined to GS, it should be able to make GS 2.7 and my parameterization
purge/dynamic param filter work can go into GWC 1.8.
>
> I see your comments about moving the workspace, did not consider it in
> fact (2.5 hours hack on a Sunday morning... that's why I asked for a review
> :-p ),
> but I don't see a problem taking it into account in a similar way to how
> we consider workspace name changes in layers... am I missing something?
>
I just wanted to make sure that case was covered but I don't think it
presents any particular issues to your approach. It was one of the rare
but annoying special cases that made my approach complicated.
--
Kevin Smith
Software Engineer | Boundless <http://boundlessgeo.com/&gt;
ksmith@...
+1-778-785-7459
@boundlessgeo <http://twitter.com/boundlessgeo/&gt;
<http://twitter.com/boundlessgeo/&gt;
[image: http://boundlessgeo.com/]
<http://boundlessgeo.com/&gt;