Hello,
moving the psml files out of the war works just fine.
I'd like to do the same for some .vm templates, but it seems that jetspeed
1.5 doesn't like it when you add a path that's outside the webapp. I
changed services.TemplateLocator.templateRoot in JS.properties and
services.VelocityService.file.resource.loader.path in TR.properties, but
then errors occurr.. I tried paths like c:/test/WEB-INF/templates and
c:/test/WEB-INF/templates/vm, and also ${webappRoot}/../directory
Could it be that turbine doesn't allow paths outside the application? Any
tips on how to achieve this?
Cheers,
Bo van Weert
David Sean Taylor <[EMAIL PROTECTED]>
21/11/2006 19:59
Por favor, responda a
"Jetspeed Users List" <[email protected]>
Para
Jetspeed Users List <[email protected]>
cc
Asunto
Re: Multiple Jetspeed front end, same database
[EMAIL PROTECTED] wrote:
> Hello,
>
> Could this also somehow be accomplished for jetspeed 1.6? (I guess not
> with Spring)
With 1.6, its the same concept
Just edit your JR.p :
And change:
services.PsmlManager.root=/WEB-INF/psml
to something like:
services.PsmlManager.root=/usr/locale/portal-data/psml
Note that in 1.6, we first try to locate file on the file system, and if
we fail to find it, we then look for the same path as a webapp relative
path
1.6 also has a Database PSML Manager
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
