There are two bugs in TurbineTemplateService:
1. The default layout template is not extended by the default extension.
2. The default.layout.template in TR.p is not used at all - it is hardwired
to "default."
The patch below fixes it. I'm not sure about the line
pkgs[arrayIndex] = pkg.append("Default").toString();
It seems to hardwire the default layout module to "Default", however I'm
not sure if it is used with templating at all?
ingo.
Index: TurbineTemplateService.java
===================================================================
RCS file:
/products/cvs/turbine/turbine/src/java/org/apache/turbine/services/template/TurbineTemplateService.java,v
retrieving revision 1.16
diff -u -r1.16 TurbineTemplateService.java
--- TurbineTemplateService.java 2001/02/08 23:55:43 1.16
+++ TurbineTemplateService.java 2001/02/16 16:50:57
@@ -196,6 +196,10 @@
// the default layout template
defaultLayoutTemplate = props
.getProperty("default.layout.template", "/default." +
extension);
+ if (defaultLayoutTemplate.endsWith("."))
+ {
+ defaultLayoutTemplate += extension;
+ }
}
/**
@@ -468,7 +472,7 @@
pkgs[arrayIndex] = distinctPkg.append(className).toString();
arrayIndex++;
}
- paths[arrayIndex] = path.append("/default." +
extension).toString();
+ paths[arrayIndex] = path.append(defaultLayoutTemplate).toString();
pkgs[arrayIndex] = pkg.append("Default").toString();
arrayIndex++;
}
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
