Re: [Geoserver-devel] [ExternalEmail] Re: Propose to add an option for latLongBoundingBox range checking before database query.

Hi, By "inaccurate bounding box" I was meaning that rectangular box can contain lot of extra area outside the real region of interest http://www.openstreetmap.org/#map=5/-42.423/165.059. But I am not sure how often it would be an advantage to use a better fitted ROI. For example in your use c

Re: [Geoserver-devel] [ExternalEmail] Re: Propose to add an option for latLongBoundingBox range checking before database query.

Hi Jukka, What one of our developer have found with oracle enterprise edition is that the database actually optimize the query when a query is made outside the bounds of the dataset. However when we ran the same query on a oracle standard edition, the query crashed the database. We have logged

Re: [Geoserver-devel] Propose to add an option for latLongBoundingBox range checking before database query.

Jody, Thanks for your reply. And great suggestion to use the native projection for the accurate reason. thanks, Lingbo From: Jody Garnett [mailto:jody.garn...@gmail.com] Sent: Thursday, 5 February 2015 4:24 PM To: Jiang, Lingbo (Digital, Marsfield) Cc: Geoserver-devel; Andrea Aime Subject: Re:

Re: [Geoserver-devel] Propose to add an option for latLongBoundingBox range checking before database query.

Hi Jukka, Yeah, you are right. it definitely should be optional. It is convenient to use BBOX rather than "Bounding Polygon" because BBOX is already in there. And the "Bounding Polygon" checking is much more expensive. Plus to specify and construct a correct "Bounding Polygon" is also a c

Re: [Geoserver-devel] (GEOS-6868) Upgrading commons-lang version - add tests?

It can be reproduced by following the steps in the LDAP documentation: http://docs.geoserver.org/latest/en/user/security/tutorials/ldap/index.html. The failure occurs at step 9 when you save the changes to the Authentication Chain. On 5 February 2015 at 14:15, Torben Barsballe wrote: > Adding Ke

Re: [Geoserver-devel] (GEOS-6868) Upgrading commons-lang version - add tests?

Adding Kevin to this conversation at request of Ben. *Jody*: I am mainly just concerned with adding a test for the bug that prompted this fix. From the JIRA ticket: GeoServer is using commons-lang-2.1.jar but some GeoServer functionality (namely LDAP authentication) requires more recent versions,

Re: [Geoserver-devel] (GEOS-6868) Upgrading commons-lang version - add tests?

I guess I am trying to say it is not worth introducing some new commons-lang functionality just to ensure we are working with the new version. The only thing I see that is fun is in commons-lang 3 (where Java 6 is a requirement). -- Jody Garnett On 5 February 2015 at 12:04, Torben Barsballe wrot

Re: [Geoserver-devel] (GEOS-6868) Upgrading commons-lang version - add tests?

I guess under LDAP authentication? Sounds like it is our only exposure to the issue ... -- Jody Garnett On 5 February 2015 at 12:04, Torben Barsballe wrote: > https://jira.codehaus.org/browse/GEOS-6868 > > I am in the process of upgrading the commons-lang to a newer version. So > far a strait u

Re: [Geoserver-devel] Propose to add an option for latLongBoundingBox range checking before database query.

Hi, I think that such check should be optional. The bounding box that gets saved when the layer is created may not stay valid if the data are updated and new features are added with WFS-T or just directly to the data source. And obviously the check should only stop the queries if BBOX is total

[Geoserver-devel] (GEOS-6868) Upgrading commons-lang version - add tests?

https://jira.codehaus.org/browse/GEOS-6868 I am in the process of upgrading the commons-lang to a newer version. So far a strait update (in both geotools and geoserver) has not broken anything (mvn clean install runs with no build or test failures) Given that the existing version of commons-lang

[Geoserver-devel] Build failed in Jenkins: geoserver-2.5.x #147

See Changes: [andrea.aime] [GEOS-6873] GeoServer leaking commons http-client connection pools in ResourcePool [andrea.aime] Java 6 compatibility -- [...truncated 3147 lines...] Downloading

[Geoserver-devel] [jira] (GEOS-6873) GeoServer leaking commons http-client connection pools in ResourcePool

Title: Message Title Andrea Aime created an issue

Re: [Geoserver-devel] Security Decorator Issue

On Thu, Feb 5, 2015 at 9:23 AM, uros wrote: > Thank you for your answer. > > I hoped that I am doing something wrong :) > I found another issue with ModificationProxy that doesn't work with > security > wrapped objects (e.g. SecuredLayerInfo for LayerInfo). I found this causing > problems with gr

Re: [Geoserver-devel] Security Decorator Issue

Thank you for your answer. I hoped that I am doing something wrong :) I found another issue with ModificationProxy that doesn't work with security wrapped objects (e.g. SecuredLayerInfo for LayerInfo). I found this causing problems with group layer creation (probably not just there). I will try t

Re: [Geoserver-devel] Propose to add an option for latLongBoundingBox range checking before database query.

On Thu, Feb 5, 2015 at 5:29 AM, wrote: > Hi Geoserver community, > > For every WMS layer that has latLongBoundingBox set up in the config, > GeoServer may restrict the request to the configured latLongBoundingBox. At > the moment, it doesn't, and this results in unnecessary query and wastes > c