Re: [Geoserver-devel] Reverting a change making our user life difficult with GDAL

2017-09-07 Thread Amiram Rahav
Well, I think that most of us know Geoerver does work with GDAL 2.x, at least some of the formats do. Maybe add the bindings back so people don't get hard errors, and then add a note saying Geoserver should work with GDAL 2.x however once you build GDAL you should replace the bindings manually? Th

Re: [Geoserver-devel] upgrade geofence hibernate

2017-07-25 Thread Amiram Rahav
I can try that H2 migration again, but my first attempt was not really successful. I had to replace H2 for integrated geofence to work correctly. with the current version the more rules you have, the more likely that an insert of a new rule will fail. Using latest H2 did work, but ended up having

Re: [Geoserver-devel] upgrade geofence hibernate

2017-07-18 Thread Amiram Rahav
which needs to be done either way. > > I am wondering if it wouldn't be an option to upgrade to hibernate 5.1 > /jdbc4 for now, and make a further upgrade later (which would likely > require little work anyway). > Just a suggestion. > > Kind Regards > Niels > > On 02-07

Re: [Geoserver-devel] upgrade geofence hibernate

2017-07-02 Thread Amiram Rahav
wever based on the version/age that is probably minimal. I still think the Geofence work should be done against JDBC 4.2 and not 4.0, however the Geoserver integrated GeoFence version will likely have to wait until that Hibernate PR is merged. On Sun, Jul 2, 2017 at 9:20 AM, Amiram Rahav

Re: [Geoserver-devel] upgrade geofence hibernate

2017-07-02 Thread Amiram Rahav
I should have said Postgres :-) On Sun, Jul 2, 2017 at 9:15 AM Andrea Aime wrote: > On Sun, Jul 2, 2017 at 3:04 PM, Amiram Rahav > wrote: > >> Hi Niels, >> >> Geotools is already using JDBC 4.2 >> > > Is GeoTools using JDBC 4.2 for all databases alrea

Re: [Geoserver-devel] upgrade geofence hibernate

2017-07-02 Thread Amiram Rahav
Hi Niels, Geotools is already using JDBC 4.2, so using anything but 4.2 is going to be a bit problematic. Well, looking at hibernate, when building Geofence integrated version, the Postgres JDBC driver pulled in by hibernate will have to be excluded to not cause conflicts with Geotools: https://g

Re: [Geoserver-devel] Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

2016-05-20 Thread Amiram Rahav
st got a 302 after a post that leads back to the home page, which is > normal, but no id. > > Regards > Niels > > > On 20-05-16 04:04, Amiram Rahav wrote: > > Hey Niels, > Thank you for taking the time and working on this! > > Just tested today's build and n

Re: [Geoserver-devel] Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

2016-05-19 Thread Amiram Rahav
stored within the user’s session are the >> same; if they are not, the request should be rejected.* >> >> >> Some background for wicket: >> - >> http://javathoughts.capesugarbird.com/2007/08/protecting-wicket-application-against.html >> - http://issues.apache.or

Re: [Geoserver-devel] Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

2016-04-28 Thread Amiram Rahav
orks (even as a workaround). And we > should report this to Jira :( > > -- > Jody Garnett > > On 27 April 2016 at 17:25, Amiram Rahav wrote: > >> Hey Guys, >> >> Trying out 2.9 Beta2 with Hazelcast clustering I noticed that every UI >> request results w

[Geoserver-devel] Hazelcast/JDBConfig clustering issues caused by HTTP 302 response and unique wicket resource IDs

2016-04-27 Thread Amiram Rahav
Hey Guys, Trying out 2.9 Beta2 with Hazelcast clustering I noticed that every UI request results with an HTTP 302 response and a unique ID appended to the URL. when using a single instance this isn't that big of an issue, however when having multiple instances behind a load balancer this results w

Re: [Geoserver-devel] GeoServer imageio and GDAL 2.0.x

2016-04-05 Thread Amiram Rahav
Hi Simone, We have been using GDAL 2.0 in several of our projects in production for the past 3 months or so without an issue, this is with Geoserver 2.8.x. However, and as Dave mentioned, this was only tested with MrSID and DTED (DTED was also used for WCS output). We've been using it on RHEL an