I got a Velocity application running on SilverStream a while back.  I don't remember
all the details but, in your case, it sounds like Turbine cannot find your properties 
file.
I don't think I ever figured out how to make SilverStream find my velocity.properties
file, so I modified the default properties file and rebuilt the velocity jar.

Also, I wrote a resource loader that knew how to go in to the database and load
resources from there.  I changed velocity.propertues to point to this new resource
loader:

  resource.loader = file
  file.resource.loader.description = Velocity File Resource Loader
  //file.resource.loader.class = 
org.apache.velocity.runtime.resource.loader.FileResourceLoader
  file.resource.loader.class = 
org.apache.velocity.runtime.resource.loader.AgResourceLoader
  file.resource.loader.path = template
  file.resource.loader.cache = false

All a bit of a hack, but it worked.  I may still have the source if it would help...

-kevin


02/10/2001 14:39:34, "Christian GARDERES" <[EMAIL PROTECTED]> 
wrote:

>
>We recently had to test the JEE reality on a SilverStream application
>server...
>So we created a war archive (full of all your nice code) and tried to
>deploy it. What a bad idee ;-(
>
>It seems that turbine and velocity, dont accomodate very well with a
>system that puts all its ressources in a database.
>
>ServletContext.getRealPath returns null on silverstream so we added the
>'basedir' init param to the turbine servlets. Then
>TurbineVelocityService complained with this message "Velocity runtime
>log file  is misconfigured: 'null' is not a valid log file" and several
>other classnotfound exception.
>
>Has anybody tried to run turbine on a application server that doesn't
>rely on a filesystem?
>
>Any idea would be a great help for us.
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]




---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to