Hi Craig,
Thanks for giving me a brief
description about default.vm.
If i have any doubts i will
mail you.
Thousands of Thanks
-----Original Message-----
From: Craig Connell [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 6:31 PM
To: 'Jetspeed Users List'
Subject: RE: Regarding Default.vm
Look in you TurbineResources.properties for the following line
services.VelocityService.default.layout.template = /default.vm
That is where you can change the default ... however, the best way to do it
would be to create your own properties file and make the change there so
that it overrides the Jetspeed default. Here are some snippets of an
internal doc I am writing that describes how to do that (although most of
the information can be found at the Jetspeed site):
_________________________________________
When Jetspeed 1.4 is loaded, it starts by loading property files into
memory. These property files contain valuable startup information that tells
Jetspeed about security, memory, storage facilities, and user creation
defaults, among other things.
The default property files that ship with Jetspeed are contained in the
/conf directory and include:
JetspeedResources.properties
JetspeedSecurity.properties
TurbineResources.properties
The default settings that are included in these files may well be suiteable
for many applications, but the XXX Portal requires some changes and addition
to these files. The proper way to add these changes is to create a new
properties file. The XXXX Portal uses new properties file named
xxx-portal.properties , which uses my.properties as a template. (
my.properties is included with Jetspeed for just this purpose.)
If you examine the web.xml file in the /WEB-INF directory, you will notice
that Jetspeed has an init param that references one of the property files.
That section of web.xml look like this:
<servlet>
<servlet-name>
jetspeed
</servlet-name>
<servlet-class>
org.apache.turbine.Turbine
</servlet-class>
<init-param>
<param-name>properties</param-name>
<param-value>WEB-INF/conf/TurbineResources.properties</param-value>
</init-param>
<init-param>
<param-name>resources</param-name>
<param-value>org.apache.jetspeed.services.resources.JetspeedResourceService<
/param-value>
</init-param>
<init-param>
<param-name>logging</param-name>
<param-value>org.apache.jetspeed.services.logging.JetspeedLoggingService</pa
ram-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
In order to use the custom properties file, the web.xml file needs to be
edited such that the init properties parameter indicates that jetspeed
should use the xxx-portal.properties file, as shown below:
<servlet>
<servlet-name>
jetspeed
</servlet-name>
<servlet-class>
org.apache.turbine.Turbine
</servlet-class>
<init-param>
<param-name>properties</param-name>
<param-value>WEB-INF/conf/xxx-portal.properties</param-value>
</init-param>
<init-param>
<param-name>resources</param-name>
<param-value>org.apache.jetspeed.services.resources.JetspeedResourceService<
/param-value>
</init-param>
<init-param>
<param-name>logging</param-name>
<param-value>org.apache.jetspeed.services.logging.JetspeedLoggingService</pa
ram-value>
</init-param>
<load-on-startup>1</load-on-startup>
</servlet>
Customizing Jetspeed With xxx-portal.properties
Any time that you want to override any properties that exist in any of the
default Jetspeed property files (JetspeedResources, JetspeedSecurity, or
TurbineResources), you use xxx-portal.properties . This does not mean that
you need to put any properties that you want to use in your properties file,
only those that you want to change or add. You can continue to load all of
the other properties from the other properties file by including the
following statements at the end of xxx-portal.properties :
include = TurbineResources.properties
This ensures that all of the properties that are in TurbineResources will
still be used by Jetspeed, except for those properties you override in the
XXX Portal properties. In turn, TurbineResources includes the
JetspeedResources and JetspeedSecurity properties files. Remember, even
though it may seem more intuitive that Jetspeed would override your
properties with the default ones (since your property file includes
TurbineResources at the end), Jetspeed actually uses any values that you
place in your properties file. The my.properties template that comes with
Jetspeed already has the include statement for you - just don't remove it!
Velocity Service Changes
Some pretty significant changes have been made to the default layout of
Jetspeed to support the look and feel that XXX wants, so we need to let
Jetspeed know the location of the new default layout, which we have named
xxxdefault.vm
# VELOCITY SERVICE CHANGES :
# CSC - Override the default setting for the templates, which is
normally '/default.vm'.
services.VelocityService.default.layout.template = /xxxdefault.vm
This file is located in Jetspeed's WEB-INF/templates/vm/layouts/html
directory.
_______
Let me know if you have any questions.
Craig
-----Original Message-----
From: S, VENKATESH [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 28, 2004 1:13 AM
To: [EMAIL PROTECTED]
Subject: Regarding Default.vm
Hi,
Please tell where to find registry entry for Default.vm. I can't find
registry entry for default.vm.
---------------------------------------------------------------------
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
