Tomcat on lettuce updates
The "installed" version of tomcat on lettuce (not the one I've been hacking on in a userdir) runs as a restricted user (as in the way that an httpd process runs under a "nobody" user) needed write permissions to the data and logs directory in order to function properly. We *think* that is the reason for the crash Martin reported this morning.
Sysadmin added me to the list of people that get informed automatically when this tomcat goes down, but while we do the debugging of this system I'm the only one on the list. When we're happy with cocoon-on-lettuce I'll let sysadmin know to flesh out that list.
Martin and I worked on getting the graves site running with little success, other than we have a vague idea how the catalog.xml system works now - which wasn't a waste of time. Basically, the file looks like this:
<?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE catalog PUBLIC "-//OASIS//DTD Entity Resolution XML Catalog V1.0//EN" "http://www.oasis-open.org/committees/entity/release/1.0/catalog.dtd"> <catalog xmlns="urn:oasis:names:tc:entity:xmlns:xml:catalog"> <public publicId="-//PLAY//EN" uri="entities/play.dtd"/> <system systemId="play.dtd" uri="entities/play.dtd"/> <system systemId="mondial.dtd" uri="entities/mondial.dtd"/> <system systemId="gravesdiary.dtd" uri="entities/gravesdiary.dtd"/> <uri name="http://www.w3.org/XML/1998/namespace" uri="entities/xml.xsd"/> </catalog>
The functionality is pretty clear. You add an entry to the catalog container which defines the type (public or system), the ID (gravesdiary.dtd) and a URI for the schema (entities/gravesdiary.dtd - which is a relative path to the schema).
Cocoon seems happy with our changes, but because the graves app hasn't been ported yet we can't be certain that this is really functional. Stay tuned.