Re: [Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 16:30 UTC on Tuesday

[Brad Hards]

My apologies, this one is a bit early for me (0330).

Brad




--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer code sprint 2017, who's interested in participating and/or sponsoring?

[Jody Garnett]

Hi Jody,

> I have a feeling participation might be actually linked to the topic being
> chosen
> for the sprint. So I'd rather first establish that.
>

I would very much agree.

So far I've heard:
>
>1. CITE tests
>
> While worth of a sprint I doubt this activity can attract much
sponsorship/enthusiasm. I will be working on it anyways and feel a bit over
my head :P

>
>1. Upgrade GeoTools/GeoServer to work on Java 9
>
> Yeah scratch 2; think that can be a small focused effort as you say.
>
>
>1. Switch REST API to Spring MVC
>
> I think this represents the largest pain for for our user community in the
mix - +1

>
>1. Assorted library upgrades (hsql, h2, commons-dbcp, log4j, wicket)
>
> Not sure how extensive an undertaking this is, would like to avoid falling
behind.


> Am I missing any?
>

One idea for beers (if not yet a sprint) is could support mapbox style in
geoserver (since it appeared in openlayers recently).

Thanks for pushing this along Andrea.
--
Jody
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Jenkins build is back to normal : geoserver-master #3815

[monitor]

See 


--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Build failed in Jenkins: geoserver-master #3814

[monitor]

See 

Changes:

[ugomoschini] [GEOS-7907] Import of SoftValueHashMap fixed

--
[...truncated 6935 lines...]
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 7:07:25 PM org.geoserver.wps.hz.HazelcastLoader 
validateConfiguration
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 7:07:25 PM com.hazelcast.partition.InternalPartitionService
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Initializing cluster partition table first 
arrangement...
Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Address[127.0.0.1]:5009 is SHUTTING_DOWN
Jan 09, 2017 7:07:30 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Master Address[127.0.0.1]:5009 left the 
cluster. Assigning new master Member [127.0.0.1]:5010 this
Jan 09, 2017 7:07:30 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Removing Member [127.0.0.1]:5009
Jan 09, 2017 7:07:30 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] 

Members [1] {
Member [127.0.0.1]:5010 this
}

Jan 09, 2017 7:07:30 PM com.hazelcast.initializer
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Destroying node initializer.
Jan 09, 2017 7:07:30 PM com.hazelcast.instance.Node
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Hazelcast Shutdown is completed in 22 ms.
Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Address[127.0.0.1]:5009 is SHUTDOWN
Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Address[127.0.0.1]:5010 is SHUTTING_DOWN
Jan 09, 2017 7:07:30 PM com.hazelcast.initializer
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Destroying node initializer.
Jan 09, 2017 7:07:30 PM com.hazelcast.instance.Node
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Hazelcast Shutdown is completed in 15 ms.
Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Address[127.0.0.1]:5010 is SHUTDOWN
Jan 09, 2017 7:07:30 PM com.hazelcast.spi.impl.BasicOperationScheduler
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Starting with 16 generic operation threads 
and 16 partition operation threads.
Jan 09, 2017 7:07:30 PM com.hazelcast.system
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Hazelcast 3.3.1 (20140929 - a1b45ef) 
starting at Address[127.0.0.1]:5011
Jan 09, 2017 7:07:30 PM com.hazelcast.system
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Copyright (C) 2008-2014 Hazelcast.com
Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Address[127.0.0.1]:5011 is STARTING
Jan 09, 2017 7:07:30 PM 
com.hazelcast.test.TestNodeRegistry$MockNodeContext$MockJoiner
INFO: [127.0.0.1]:5011 [dev] [3.3.1] 


Members [1] {
Member [127.0.0.1]:5011 this
}

Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Address[127.0.0.1]:5011 is STARTED
Jan 09, 2017 7:07:30 PM com.hazelcast.spi.impl.BasicOperationScheduler
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Starting with 16 generic operation threads 
and 16 partition operation threads.
Jan 09, 2017 7:07:30 PM com.hazelcast.system
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Hazelcast 3.3.1 (20140929 - a1b45ef) 
starting at Address[127.0.0.1]:5012
Jan 09, 2017 7:07:30 PM com.hazelcast.system
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Copyright (C) 2008-2014 Hazelcast.com
Jan 09, 2017 7:07:30 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Address[127.0.0.1]:5012 is STARTING
Jan 09, 2017 7:07:30 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] 

Members [2] {
Member [127.0.0.1]:5011 this
Member [127.0.0.1]:5012
}

Jan 09, 2017 7:07:30 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5012 [dev] [3.3.1] 

Members [2] {
Member [127.0.0.1]:5011
Member [127.0.0.1]:5012 this
}

Jan 09, 2017 7:07:31 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Address[127.0.0.1]:5012 is STARTED
Jan 09, 2017 7:07:31 PM org.geoserver.wps.hz.HazelcastLoader 
validateConfiguration
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 7:07:31 PM org.geoserver.wps.hz.HazelcastLoader 
validateConfiguration
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 7:07:31 PM com.hazelcast.partition.InternalPartitionService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Initializing cluster partition table first 
arrangement...
Jan 09, 2017 7:07:36 PM 

[Geoserver-devel] Build failed in Jenkins: geoserver-master #3813

[monitor]

See 

--
[...truncated 6908 lines...]
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 6:25:38 PM org.geoserver.wps.hz.HazelcastLoader 
validateConfiguration
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 6:25:38 PM com.hazelcast.partition.InternalPartitionService
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Initializing cluster partition table first 
arrangement...
Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Address[127.0.0.1]:5009 is SHUTTING_DOWN
Jan 09, 2017 6:25:38 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Master Address[127.0.0.1]:5009 left the 
cluster. Assigning new master Member [127.0.0.1]:5010 this
Jan 09, 2017 6:25:38 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Removing Member [127.0.0.1]:5009
Jan 09, 2017 6:25:38 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] 

Members [1] {
Member [127.0.0.1]:5010 this
}

Jan 09, 2017 6:25:38 PM com.hazelcast.initializer
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Destroying node initializer.
Jan 09, 2017 6:25:38 PM com.hazelcast.instance.Node
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Hazelcast Shutdown is completed in 24 ms.
Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5009 [dev] [3.3.1] Address[127.0.0.1]:5009 is SHUTDOWN
Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Address[127.0.0.1]:5010 is SHUTTING_DOWN
Jan 09, 2017 6:25:38 PM com.hazelcast.initializer
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Destroying node initializer.
Jan 09, 2017 6:25:38 PM com.hazelcast.instance.Node
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Hazelcast Shutdown is completed in 13 ms.
Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5010 [dev] [3.3.1] Address[127.0.0.1]:5010 is SHUTDOWN
Jan 09, 2017 6:25:38 PM com.hazelcast.spi.impl.BasicOperationScheduler
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Starting with 16 generic operation threads 
and 16 partition operation threads.
Jan 09, 2017 6:25:38 PM com.hazelcast.system
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Hazelcast 3.3.1 (20140929 - a1b45ef) 
starting at Address[127.0.0.1]:5011
Jan 09, 2017 6:25:38 PM com.hazelcast.system
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Copyright (C) 2008-2014 Hazelcast.com
Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Address[127.0.0.1]:5011 is STARTING
Jan 09, 2017 6:25:38 PM 
com.hazelcast.test.TestNodeRegistry$MockNodeContext$MockJoiner
INFO: [127.0.0.1]:5011 [dev] [3.3.1] 


Members [1] {
Member [127.0.0.1]:5011 this
}

Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Address[127.0.0.1]:5011 is STARTED
Jan 09, 2017 6:25:38 PM com.hazelcast.spi.impl.BasicOperationScheduler
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Starting with 16 generic operation threads 
and 16 partition operation threads.
Jan 09, 2017 6:25:38 PM com.hazelcast.system
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Hazelcast 3.3.1 (20140929 - a1b45ef) 
starting at Address[127.0.0.1]:5012
Jan 09, 2017 6:25:38 PM com.hazelcast.system
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Copyright (C) 2008-2014 Hazelcast.com
Jan 09, 2017 6:25:38 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Address[127.0.0.1]:5012 is STARTING
Jan 09, 2017 6:25:38 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5012 [dev] [3.3.1] 

Members [2] {
Member [127.0.0.1]:5011
Member [127.0.0.1]:5012 this
}

Jan 09, 2017 6:25:38 PM com.hazelcast.cluster.ClusterService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] 

Members [2] {
Member [127.0.0.1]:5011 this
Member [127.0.0.1]:5012
}

Jan 09, 2017 6:25:39 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5012 [dev] [3.3.1] Address[127.0.0.1]:5012 is STARTED
Jan 09, 2017 6:25:39 PM org.geoserver.wps.hz.HazelcastLoader 
validateConfiguration
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 6:25:39 PM org.geoserver.wps.hz.HazelcastLoader 
validateConfiguration
WARNING: The WPS status map wpsExecutionStatusMap has a max size set, it should 
be unbounded so that no status is lost before the configured timeout
Jan 09, 2017 6:25:39 PM com.hazelcast.partition.InternalPartitionService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Initializing cluster partition table first 
arrangement...
Jan 09, 2017 6:25:39 PM com.hazelcast.core.LifecycleService
INFO: [127.0.0.1]:5011 [dev] [3.3.1] Address[127.0.0.1]:5011 is 

Re: [Geoserver-devel] bug stomp jan 27th?

[Andrea Aime]

Likewise

Cheers
Andrea

On Mon, Jan 9, 2017 at 6:47 PM, Torben Barsballe <
tbarsba...@boundlessgeo.com> wrote:

> The 27th sounds good to me.
>
> Torben
>
> On Wed, Jan 4, 2017 at 10:34 AM, Ben Caradoc-Davies 
> wrote:
>
>> Count me in!
>>
>> Kind regards,
>> Ben.
>>
>> On 05/01/17 07:16, Jody Garnett wrote:
>> > Is anyone up for a bug stomp this month? Boundless has expressed a solid
>> > interest (which is great!).
>> >
>> > Who is available for Friday the 27th? Or does another day suite ...
>> > --
>> > Jody Garnett
>> >
>> >
>> >
>> > 
>> --
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> >
>> >
>> >
>> > ___
>> > Geoserver-devel mailing list
>> > Geoserver-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>> >
>>
>> --
>> Ben Caradoc-Davies 
>> Director
>> Transient Software Limited 
>> New Zealand
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>
> 
> --
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>


-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://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.

---
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] bug stomp jan 27th?

[Torben Barsballe]

The 27th sounds good to me.

Torben

On Wed, Jan 4, 2017 at 10:34 AM, Ben Caradoc-Davies 
wrote:

> Count me in!
>
> Kind regards,
> Ben.
>
> On 05/01/17 07:16, Jody Garnett wrote:
> > Is anyone up for a bug stomp this month? Boundless has expressed a solid
> > interest (which is great!).
> >
> > Who is available for Friday the 27th? Or does another day suite ...
> > --
> > Jody Garnett
> >
> >
> >
> > 
> --
> > Check out the vibrant tech community on one of the world's most
> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> >
> >
> >
> > ___
> > Geoserver-devel mailing list
> > Geoserver-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
> >
>
> --
> Ben Caradoc-Davies 
> Director
> Transient Software Limited 
> New Zealand
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

[Geoserver-devel] Reminder: GeoTools / GeoServer Meeting at 16:30 UTC on Tuesday

[Ben Caradoc-Davies]

GeoTools / GeoServer committee meeting on Skype at 16:30 UTC on Tuesday:
https://www.timeanddate.com/worldclock/fixedtime.html?msg=GeoTools+%2F+GeoServer+Meeting=2017=1=10=16=30=0=1

-- 
Ben Caradoc-Davies 
Director
Transient Software Limited 
New Zealand

--
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] Dispatcher Simulation Mode

[Justin Deoliveira]

Hey folks,

Given the feedback I think it this live in a community module for now and
we’ll see how it evolves from there. Any objections? If not consider this
my request for a new community module. Thanks.

-Justin

On Thu, Dec 22, 2016 at 11:29 AM Justin Deoliveira 
wrote:

> On Thu, Dec 22, 2016 at 9:27 AM Andrea Aime 
> wrote:
>
> On Thu, Dec 22, 2016 at 2:23 PM, Justin Deoliveira 
> wrote:
>
> Thanks for the feedback Andrea. Comments inline.
>
> Now you are getting me a bit worried... maybe it's nothing, but the
> request objects were not designed to be returned back to the users,
> depending on how deep you go dumping them, you might end up revealing
> information that the admin does not want to be seen, such as for example
> the security filters being applied by something like GeoFence, or the
> datastore connection parameters (ok, that would be quite the deep scan in
> the object tree, but in the end all the info is actually linked and
> reachable from a GetMapRequest object for example).
>
> In other words, is it something that one would want to always have and
> would come with sane restriction to avoid leaking information, something
> allowed only to admins, something that it's core vs a plugin?
>
> Good point. What if we made it an explicit “opt-in” enabled only via
> configuration or a system property, etc…
>
> Another option could be to simply redact sensitive information when the
> user isn’t the admin… Or do you think there are too many cases of sensitive
> properties to handle?
>
>
> Hard to tell.. like, would it be ok to stop at any found catalog related
> information and just return its name instead of its details, which could
> reveal
> security restrictions (e.g., SecuredFeatureTypeInfo) ?
>
>
> In my immediate case yes, and I would say in general yes. The point of the
> call is not to provide a full dump of the request properties, more just to
> provide a representation of what the request will do. I think that for
> catalog objects, geotools objects… just displaying a name or id is enough
> to do that without providing anything deeper, which as you pointed out can
> definitely contain sensitive information.
>
>
>
>
>
> Fwiw I wasn’t planning on traversing the object deep enough to get down to
> anything like data store connection information. Just
>
>
> I was thinking you'd have allowed a user requestable expansion level like
> in the importer REST API.
> In general, depending on the protocol involved and the request structure
> (which might change over time) you might need
> to modify how deep you go. I believe at one time we expanded the expansion
> level in the logger to get more useful WPS information
> for example
>
>
> Yeah, I was thinking the same, allow “depth” to be specified in the
> request with a conservative default value.
>
> Thanks for all the feedback. I think at this point I have enough to start
> working on the code. I’ll report back when I have something more concrete
> working and we can continue discussion with a patch to look at. However if
> there are any more concerns I am happy to keep discussing now.
>
> Happy holidays!
>
> -Justin
>
>
> Cheers
> Andrea
>
> --
> ==
> GeoServer Professional Services from the experts! Visit
> http://goo.gl/it488V for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions S.A.S.
> Via di Montramito 3/A
> 55054  Massarosa (LU)
> phone: +39 0584 962313 <+39%200584%20962313>
> fax: +39 0584 1660272 <+39%200584%20166%200272>
> mob: +39  339 8844549 <+39%20339%20884%204549>
>
> http://www.geo-solutions.it
> http://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 

Re: [Geoserver-devel] Dispatcher Simulation Mode

[Andrea Aime]

On Mon, Jan 9, 2017 at 4:15 PM, Justin Deoliveira 
wrote:

> Hey folks,
>
> Given the feedback I think it this live in a community module for now and
> we’ll see how it evolves from there. Any objections? If not consider this
> my request for a new community module. Thanks.
>

+1 on the community module

Cheers
Andrea

-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://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.

---
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GSIP 153 - opaque container layer group mode

[Andrea Aime]

Ok, ready for review here: https://github.com/geoserver/geoserver/pull/2048

Cheers
Andrea

On Wed, Jan 4, 2017 at 1:42 AM, Jody Garnett  wrote:

> Thanks Kevin.
>
> I have updated https://github.com/geoserver/geoserver/wiki/GSIP-153 with
> the table of responsibilities for each layer group mode.
>
> We could not come up with any good alternate wording, please proceed.
>
> --
> Jody Garnett
>
> On 3 January 2017 at 16:04, Kevin Smith  wrote:
>
>> On 17-01-03 10:30 AM, Kevin Smith wrote:
>> > I agree both that "opaque container" is a bit ugly and potentially
>> > confusing and that "basemap" is too specific.  Maybe a "flat group"?
>>
>> Jody and I just talked this over and I withdraw "flat group". My new
>> suggestion is "Restricted Single" which isn't great but is consistent
>> with "single" meaning it does not show it's children while "trees" do.
>> Jody likes "Container" which again avoids "tree" although I dislike that
>> it is inconsistent with how "container" is used in "Container Tree"
>> because a container tree is not a named layer.
>>
>> --
>> Kevin Michael Smith
>> 
>>
>>
>>
>> 
>> --
>> Check out the vibrant tech community on one of the world's most
>> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>>
>
> 
> --
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, SlashDot.org! http://sdm.link/slashdot
> ___
> Geoserver-devel mailing list
> Geoserver-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
>


-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://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.

---
--
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

Re: [Geoserver-devel] GeoServer code sprint 2017, who's interested in participating and/or sponsoring?

[Andrea Aime]

Hi Jody,
I have a feeling participation might be actually linked to the topic being
chosen
for the sprint. So I'd rather first establish that.

So far I've heard:

   1. CITE tests
   2. Upgrade GeoTools/GeoServer to work on Java 9
   3. Switch REST API to Spring MVC
   4. Assorted library upgrades (hsql, h2, commons-dbcp, log4j, wicket)

Am I missing any?

Personally I'm a bit skeptical about 2), as important as it is, it seems
better suited to be tackled by
a very small team (2 people max?) as it involves, in my understanding,
rewriting some core java classes without any license issue,
and then changing a bunch of imports. The others seem more suitable for
swarming with a larger team
(like 5-10 people).

Cheers
Andrea


On Fri, Jan 6, 2017 at 10:26 PM, Jody Garnett 
wrote:

> Thanks for keeping the conversation going over the break mike; I did mange
> to speak to the decision makers and Boundless is keen on an early March
> sprint. I also have some capacity to help with call for sponsorship and
> organization (like last year) if that can be of assistance ...
>
> I won't be able to attend next week's meeting; I trust a date can be
> established.
>
>
> --
> Jody Garnett
>
> On 19 December 2016 at 16:13, Mike Pumphrey  wrote:
>
>> I can't speak for Boundless except that I have forwarded on this on to
>> the decision makers and keepers of the budget, to see what if anything
>> we can do. And that I would very much like to go. :)
>>
>> And for what it's worth, later is better for me (end of March great,
>> beginning of March okay, February not great).
>>
>> Thanks for offering to host!
>>
>> Thanks,
>> Mike
>>
>> Mike Pumphrey
>> Education Program Director | Boundless
>> 917-338-0407
>> m...@boundlessgeo.com
>> http://boundlessgeo.com
>> @boundlessgeo
>>
>> On 12/16/2016 11:07 AM, Andrea Aime wrote:
>> > Hi,
>> > say that we setup a code spring in late February/March.
>> >
>> > Say that the topic would be upgrading the CITE tests and adding all the
>> new
>> > exciting ones we're
>> > missing (e.g., WFS 2.0, WCS 2.0, WMTS, WPS, ...), in other words,
>> getting
>> > up to speed
>> > with the OGC compliance. (if this topic puts you off, let us know what
>> > would be a better one for you).
>> >
>> > Say also we organize the sprint at the GeoSolutions offices in beautiful
>> > Tuscany for
>> > a week long.
>> >
>> > Question:
>> >
>> >- Who would be interested in joining as a participating?
>> >- Who would be interested in sponsoring? ;-)
>> >- Do you have any preferred week between say Feb 13 and end of March?
>> >
>> > My answers:
>> >
>> >- I'm in, but I won't be available Jan 30-Feb 2
>> >
>> > Cheers
>> > Andrea
>> >
>> >
>> >
>> > 
>> --
>> > Check out the vibrant tech community on one of the world's most
>> > engaging tech sites, SlashDot.org! http://sdm.link/slashdot
>> >
>> >
>> >
>> > ___
>> > Geoserver-devel mailing list
>> > Geoserver-devel@lists.sourceforge.net
>> > https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>> >
>>
>> 
>> --
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today.http://sdm.link/intel
>> ___
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>>
>
>


-- 
==
GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054  Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://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