Now that METS (and rotation) is supported, there is no need to export to LAREX from OCR-D (and back) anymore. However, that also means I will need a central storage location for all my workspaces, which is quite inconvenient. Symlinked directories still do not seem to be supported (probably because Jetty/Catalina/Tomcat prohibit this for security reasons) – they are simply ignored.
Now, the default /usr/local/tomcat/conf/context.xml sets up permissions like this:
<!-- The contents of this file will be loaded for each web application -->
<Context><Resources allowLinking="true"/>
<!-- Default set of monitored resources. If one of these changes, the -->
<!-- web application will be reloaded. -->
<WatchedResource>WEB-INF/web.xml</WatchedResource>
<WatchedResource>WEB-INF/tomcat-web.xml</WatchedResource>
<WatchedResource>${catalina.base}/conf/web.xml</WatchedResource>
<!-- Uncomment this to disable session persistence across Tomcat restarts -->
<!--
<Manager pathname="" />
-->
</Context>
Which means some linking should already be allowed. Any ideas what I could try to get past this barrier?
Now that METS (and rotation) is supported, there is no need to export to LAREX from OCR-D (and back) anymore. However, that also means I will need a central storage location for all my workspaces, which is quite inconvenient. Symlinked directories still do not seem to be supported (probably because Jetty/Catalina/Tomcat prohibit this for security reasons) – they are simply ignored.
Now, the default
/usr/local/tomcat/conf/context.xmlsets up permissions like this:Which means some linking should already be allowed. Any ideas what I could try to get past this barrier?