I appreciate the reply, but 'navigations' isn't in the path for the
resource loader. I took your reply on Velocity-User to mean "this is
a Turbine issue - go ask over there...".
Here are the only resource.loader entries in TR.properties
services.VelocityService.resource.loader = file
services.VelocityService.file.resource.loader.description = Velocity File
Resource Loader
services.VelocityService.file.resource.loader.class =
org.apache.velocity.runtime.resource.loader.FileResourceLoader
services.VelocityService.file.resource.loader.path = /templates
services.VelocityService.file.resource.loader.cache = false
services.VelocityService.file.resource.loader.modificationCheckInterval = 2
services.VelocityService.resource.loader = classpath
services.VelocityService.classpath.resource.loader.description = Velocity
Classpath Resource Loader
services.VelocityService.classpath.resource.loader.class =
org.apache.velocity.runtime.resource.loader.ClasspathResourceLoader
Jim
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
Behalf Of Geir Magnusson Jr.
Sent: Sunday, August 19, 2001 8:14 PM
To: [EMAIL PROTECTED]
Subject: Re: Velocity #include, #parse problem (template not found)
Jim Reesman wrote:
>
> Hi,
>
> I'm trying to use Velocity #include and #parse directives, but can't seem
to
> get them
> to work. Velocity.log reports
>
> [info] ResourceManager : found navigations/breadcrumbs.vm with loader
blah,
> blah...
> [error] #include : cannot find navigations/breadcrumbs.vm template!
>
> when handling a .vm that contains
>
> $navigation.setTemplate("breadcrumbs.vm")
>
> and
>
> #include("navigations/breadcrumbs.vm")
I answered this over on the Velocity list.
Velocity checks for templates based on the nodes listed in it's
loader.path property, so if "navigations" is a node in the path list for
the file resource loader, then you mustn't specify "navigations" again
in the #include(), unless there is a "navigations" directory under
"navigations".
geir
> The .path property is set properly and reported correctly in velocity.log
> (and all
> 'automatically' loaded templates are working fine...).
>
> Is there a known explanation for this, or can someone please give me some
> pointers
> on what to check as I begin to debug this?
>
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
Well done is better than well said - New England Proverb
---------------------------------------------------------------------
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]
