on 7/5/2000 7:13 PM, "Oki DZ" <[EMAIL PROTECTED]> wrote:
> I already have Tomcat+Turbine running, but it was with some tweaking on
> the Turbine.java.
Which wasn't necessary...
> I guess the problem is that Turbine was supposed to be run with JServ, so
> that the way it finds TurbineResources.properties file is by JServ's way;
> I had tried to put it in $TOMCAT_HOME/conf, but it didn't work. Then I
> added:
> props = "/usr/local/tomcat/conf/TurbineResources.properties";
> right before the try-catch statement, ie. the try for:
> TurbineResourceService.setPropertiesFileName(props);
That is totally unnecessary. If you use the methodology documented here:
<http://java.apache.org/turbine/war-webmacro.html> things work just fine
with Tomcat.
> This was a quick fix, but I think I wouldn't have had much patience to
> wait for the correct release.
Patience is a virtue.
> Well, not really, "Visitor object couldn't be found"; I use Sybase and the
> SQL scripts included in the distribution were not for Sybase. But it was
> okay, the problem was that the statement for inserting user "turbine"
> with password "turbine" was missing. Ahm, not only that, Sybase is
> case-sensitive on table and column names, and the scripts use
> upper/lower-cases.
Did you use the Sybase stuff in docs/schema/? Anyway, this stuff isn't
really necessary because it is only a small part of Turbine.
> BTW, Turbine has user/password security, why would Tomcat have
> org.apache.tomcat.security.*? (The descriptions on Tomcat security exist
> on the web site, but the nightly-builds source codes don't have any
> "security"; slightly confusing, but since I'm dealing with
> nightly-builds...)
Tomcat security is totally different than the way that Turbine does
security. Tomcat's security came WAY after Turbine's.
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
