> WebMacro adds some difficulty in that it searches the
> classpath for its
> properties. I am guessing that as long as you have a webmacro.jar and
> properties file per zone everything will be okay. (This is
> something that
> needs to be fixed in WM, unless I am misreading the situation.)
Actualy, fixing this doesn't require modyfing WM at all. We need to
change TurbineWebMacroService.initWebMacro():
String WMProperties = TurbineResources.getString("webmacro.properties",null);
if(WMProperties != null)
{
wm = new WM(WMProperties);
}
else
{
// none specified: fallback to WM style properies search
wm = new WM();
}
Another thing we may want to add here is checking if the specifed path is
relative and if so, transforming it to be relative to our webapp root (provided
that we are running under Servlets 2.2 container). Doing this requires
an access to ServletContext of Turbine Servlet inside TurbineWebMacroService.init(),
which is supposed to be handled by Kevin's Initialization API.
I'd really like to know how it's progressing. Kevin: do you have any patches to try
yet?
Could I give you any help?
Rafal
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
