on 6/1/2000 9:31 AM, Rafal Krzewski at [EMAIL PROTECTED] wrote:
>>> We could also define an additional parameter in WebMacro.properties,
>>> which would indicate if this translation should be performed or not.
> I refined this idea a bit more: Let's define WebAppTemplatePath parameter.
> If this parameter is present, and getRealPath() works, we assume that we
> are running inside a webapp and paths resulting from the translation should
> replace TemplatePath. If not, we assume that we are running under JServ,
> and TemplatePath should be used. Therefore, when we are deploing our
> app inside 2.2 engine, we ignore TemplatePath and it's just working, and if
> we are deploying under JServ, we ignore WebAppTemplatePath, and
> set TemplatePath.
sounds good.
> I need help with this one! Is it possible right now? Or do we need to modify
> Turbine class for that? I think that we can't use static filed for this,
> because
> there may be many applications using Turbine running in the same container
> (not Tomcat 3.1, but future releases - yes).
You can't until Kevin finish's his init() API.
>> properties == TurbineResources.properties
>> webmacro.properties == WebMacro.properties
>
> These are fine with me. Yet again, maybe we shouldn't specify Webmacro
> properies as servlet init arg? We could make it TurbineResources.properites
> entry, as we did with FreeMaker. This would be more consistent, leaving
> TurbineResources.propertis the master config file.
+1
-jon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
