You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@turbine.apache.org by "Schmidt, Uwe" <US...@GEA-WIEGAND.DE> on 2001/10/01 10:18:56 UTC
AW: Template Subdirectories
I have the same problem:
What I like to try is to install the applications
as real turbine-applications (I am still developing
the portal, so i just planning ;-) ). Every application
has its own directory (e.g. webapps/app1, webapps/app2)
The portal-API has than to be installed as a jar-file
in one of the central library dirctories, so that the
applications have access the om-classes,
the SecurityScreen-class and so on ...
The advantage of that should be that the single applications
could be maintained without shutting down the whole
server and the applications are clearly separated from each
other.
But I also see several questions:
Could a session started at the portal-application be shared
among several other applications ?
What about some of the turbine-properties ?
What about the $ui...?
What about default layouts and navigations ?
Uwe
-----Ursprüngliche Nachricht-----
Von: Daniel B. Ramagem [mailto:daniel_ramagem@ssaihq.com]
Gesendet am: Mittwoch, 26. September 2001 23:07
An: turbine-user@jakarta.apache.org
Betreff: Template Subdirectories
I want to host several web applications under the same Turbine instalation.
The starting point (homepage) would be a "portal" from where the user could
go to different websites/applications. I wanted to place each web
application under a different directory so that each would have its own set
of Velocity modules (screens, layouts, navigations, actions) like so:
webapps/templates/app1/screens
webapps/templates/app1/layouts
webapps/templates/app1/navigations
webapps/templates/app2/screens
webapps/templates/app2/layouts
webapps/templates/app2/navigations
etc.
But the problem is that Turbine searches sequentially for template names in
the TR property "services.VelocityService.file.resource.loader.path". So if
I have templates with the same name Turbine will return the first one it
finds from the path.
Can I fully qualify a template name to distinguish it from app1 or app2?
Or will I have to go for the solution:
webapps/templates/screens/app1
webapps/templates/screens/app2
webapps/templates/layouts/app1
webapps/templates/layouts/app2
webapps/templates/navigations/app1
webapps/templates/navigations/app2
And in my templates use $link.setPage("app1,Index.vm"), etc.?
Thanks for any help!
Daniel Bloomfield Ramagem
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: turbine-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: turbine-user-help@jakarta.apache.org