Hi all,
some time ago I tried removing the GenericDao, upgrading the
hibernate+spatial version (see
https://github.com/geoserver/geofence/issues/255).
It was a successful proof of concept, but it was applied on an old code
base.
I can try cherry picking the changes on the current main branch.
I'll
On Wed, Feb 21, 2024 at 12:32 AM Jody Garnett
wrote:
> Is there a problem updating content from one version of hibernate to the
> next?
>
Yes, it's a web of dependencies, I don't know all the details (Emanuele
please help here)
but updating Hibernate leads to other issues, as GeoFence uses Hiber
Hi Niels,
I guess the limitation here is the time to upgrade, check what need to
change on codebase and test after the upgrade. I can start to experiment
upgrading geofence in the next days.
Regarding version I see 5.3.20 has already CVE record linked, maybe we can
target upgrade to latest 5.3.x
Is there a problem updating content from one version of hibernate to the
next?
I have not heard of any plans to update, but I do not know a reason to stay
on hibernate 3.6.9 either.
--
Jody Garnett
On Feb 19, 2024 at 6:22:54 AM, Niels Charlier via Geoserver-devel <
geoserver-devel@lists.sourcef
Hello,Currently, the managed version of Hibernate is 3.6.9. This version is rather ancient, from 2011. It is used by one extension: geofence-server; and one community module: monitor-hibernate.Taskmanager, a community module that I maintain, uses a more recent version of hibernate: 5.3.20. This do
