GeoTools / GeoServer Meeting 2015-07-07
===
Attending
-
Ben Caradoc-Davies
Jukka Rahkonen
Kevin Smith
Torben Barsballe
Agenda
--
- Security
- Pull requests
- ESRI WMS cascading problem
Actions
---
AA: Create Jira components Security (Authent
Is there any way we can create the new one but leave it wrapped in a
deprecated class for the old clients to use? Then over time switch over the
new one. The deprecated class can continue to eat the exception but maybe
log it at higher than fine - or emit a warning that if the client was using
the
On Tue, Jul 7, 2015 at 11:47 AM, Ian Turton wrote:
> We even have an open Jira for it at
> https://osgeo-org.atlassian.net/browse/GEOT-4715 :-)
>
> I like all of the options - the purist in me leans to a - but I can see
> that is a hassle to implement.
>
To implement for me it's actually probabl
We even have an open Jira for it at
https://osgeo-org.atlassian.net/browse/GEOT-4715 :-)
I like all of the options - the purist in me leans to a - but I can see
that is a hassle to implement.
Of the others I think C - the list - is a cleaner and more extensible
option. It looks like the easier op
Hi,
when creating a datastore, if we pass a set of invalid params to a specific
factory,
we get back useful exceptions, telling us that the connection could not be
made,
the file was not found, the caps document was invalid, and so on.
When doing the same with a coverage Format object, we get back
On Tue, Jul 7, 2015 at 10:38 AM, stefano.costa <
stefano.co...@geo-solutions.it> wrote:
> Yet another solution I didn't think about earlier could be to leave
> everything as is and clearly state in the mongodb module documentation that
> to be able to filter on nested properties (and in general o
Hi Jody,
Sorry if I wasn't clear enough in my previous e-mails, I'll try to clarify.
When a mongodb collection is published and no schema already exists for it, a
schema is inferred by MongoInferredMapper and added to the schema store.
MongoInferredMapper recursively inspects all properties of
