Re: 52N-SOS.4.3.10 Github HibernateMappings for custom Oracle database
> I have been working with the 52N SOS server for while. Now I would like
> to try custom Hibernate Mappings for an existing Oracle database. For
> some initial better understanding I have a few questions:
> 1) Do I need to customise the mappings files already before the mvn
> build or can I edit the mappings files "as I go" and then "only" have to
> restart Tomcat/servlet container?
No, you can also edit the mapping files in the deployed webapp and the
you "only" have to restart Tomcat/servlet container.
> 2) Can I switch off transactional features and then don't need to have
> mapping files for transactions in place?
Yes, if you select the "Oracle Spatial Custom Core" (see 3), only the
"core" and "series" "old" hibernate mapping folders are loaded.
The transactional operations are also disabled by default in the SOS.
> 3) Can I configure the Oracle database too through the standard "install
> wizard" webgui (like I would do it when I do a fresh install on a
> postgis db for example?) ?
Yes, if you use customized mapping files you should select "Oracle
Spatial Custom Core" in the installation because if you select another
option, the mapping files would be validated against the existing
database model which mostly fails for customized mappings.
> 4) Can the database be read-only and the SOS server would work without
> having to "touch" the database?
Yes, the database can be read-only.
More information about the 52N SOS database model and the Hibernate
mapping files can be found here: