Go Back to SlideProjectPages

DefaultTomcatRealm Tips and Tricks.

SlideRealm Tips and Tricks.

Tomcat Slide-Admin out of the box.

Problem:

When I installed the slide.war and slide-admin.war on my Tomcat 4.1, the slide-admin wouldn't start and complained about the fact it couldn't find Domain.xml. I found in the Slide-Users mailist archives to try putting Domain.xml in the tomcat /bin directory....I tried that and it didn't work. It didn't work when I was running Tomcat as a Service that is, it did work when I ran it standalone with startup.bat in the /bin directory. But I wanted it to run as a service....

Solution:

You should provide a slide.properties file that contains the absolute path to your Domain.xml file (see http://jakarta.apache.org/slide/conf-lib.html). Then put this file somewhere where it can be found by Slide on initialization. More concretely this means: if you have the slide-kernel.jar in common/lib, you will want to put your custom slide.properties file in common/classes. Note that Slide expects to find the slide.properties file in the org.apache.slide package (IIRC), so in effect you'll have common/classes/org/apache/slide/slide.properties.

Inside the property file you'll have a org.apache.slide.domain property set to the absolute path of Domain.xml. For example:

    org.apache.slide.domain = C:/Slide/Domain.xml

Note that you have to use a forward slash even on windows, because the backslash is an escape character! Double backslash should work too, though. Paths with spaces are known to be problematic.

Hope this helps – ChristopherLenz

It does and thanks. I (ollie) would also offer that replacing the slide.properties in the slide-kernal.jar with one modified as you specify should work.

Alternate solution:

The Domain class has a method Domain.init() where you can specify the absolute url of the Domain.xml file. If used in combination with reading servlet settings one can compile a version of the servlet that reads the url from the configuration which could ease setting up and configuring the servlet on different machines/setups.

  • No labels