I think that regardless of what we do we will have version conflicts with
the integrated version. There isn't a really simple/easy way around that.

For the stand alone version, I think it's safe to go with the latest
version, however will defer to the geofence modules maintainers on this.

Thanks,
Ami.




On Tue, Jul 18, 2017 at 11:03 AM, Niels Charlier <ni...@scitus.be> wrote:

> We agree now about the refactoring of the DAO, but do we definitely agree
> about which version to upgrade to?
>
> I need to make sure everyone is on the same page before I start work.
>
> Ami suggests upgrading the geofence modules to JDBC 4.2, but leave the
> integrated geofence to work with the older geofence modules until the
> hibernate PR for jdbc 4.2 has been merged.
>
> Do the maintainers of the geofence modules agree with this plan?
>
> Alternatively, I suggest we could upgrade to jdbc4 for now, since that
> seems to work with most modules in geotools/geoserver anyway.
>
> Kind Regards
> Niels
>
> On 03-07-17 12:01, Niels Charlier wrote:
>
> Ami,
>
> In any case, the biggest load of the work will be rewriting the DAO's
> 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-17 19:01, Amiram Rahav wrote:
>
> Taking another look at Hibernate, things might be a bit more complicated.
> There is a PR to add some JDBC 4.2 type names -
> https://github.com/hibernate/hibernate-orm/pull/1940
> <https://github.com/hibernate/hibernate-orm/pull/1940>
> <https://github.com/hibernate/hibernate-orm/pull/1940>.
>
> We will likely see some version conflict with other Geotools dependencies:
> For Oracle the suggestion is to use ojdbc6/7 (JDBC 4.0/4.1), but the
> hibernate PR from above will pull in ojdbc8.
> For MSSQL the suggestion is to use sqljdbc41, however I've been using JDBC
> 4.2 at several clients.
> mysql looks to be 4.0, however it might have limited implementation of
> 4.1.
> H2 looks like JDBC3, it might implement JDBC 4.0, however 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 <ara...@boundlessgeo.com
> <mailto:ara...@boundlessgeo.com> <ara...@boundlessgeo.com>> wrote:
>
>     I should have said Postgres :-)
>
>
>
>     On Sun, Jul 2, 2017 at 9:15 AM Andrea Aime
>     <andrea.a...@geo-solutions.it
>     <mailto:andrea.a...@geo-solutions.it> <andrea.a...@geo-solutions.it>>
> wrote:
>
>         On Sun, Jul 2, 2017 at 3:04 PM, Amiram Rahav
>         <ara...@boundlessgeo.com <mailto:ara...@boundlessgeo.com>
> <ara...@boundlessgeo.com>> wrote:
>
>             Hi Niels,
>
>             Geotools is already using JDBC 4.2
>
>
>         Is GeoTools using JDBC 4.2 for all databases already, did you
>         check?
>         Using hibernate is partly about database independence, I know
>         that the postgis store
>         was recently updated, what about the others? (oracle,
>         sqlserver, mysql, H2, ...)
>
>         Cheer
>         Andrea
>
>         --
>         Regards,
>
>         Andrea Aime
>
>         ==GeoServer Professional Services from the experts! Visit
>         http://goo.gl/it488V for more information.==Ing. Andrea Aime
>         @geowolfTechnical LeadGeoSolutions S.A.S.Via di Montramito
>         3/A55054  Massarosa (LU)phone: +39 0584 962313
> <+39%200584%20962313>
>         <tel:+39%200584%20962313>fax: +39 0584 1660272
> <+39%200584%20166%200272>
>         <tel:+39%200584%20166%200272>mob: +39  339 8844549
> <+39%20339%20884%204549>
>         <tel:+39%20339%20884%204549>http://www.geo-solutions.ithttp:
> //twitter.com/geosolutions_it
>
>         <http://twitter.com/geosolutions_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
>
>
>
>
>
>
> ------------------------------------------------------------------------------
> 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 
> listGeoserver-devel@lists.sourceforge.nethttps://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

Reply via email to