[EMAIL PROTECTED] wrote:
> Quoting Johnny Cass <[EMAIL PROTECTED]>:
>
>
>>[EMAIL PROTECTED] wrote:
>>
>>>i'm working on a turbine 2.2 release.
>>>all bug-fixes are back-ported from HEAD to the 2.x branch.
>>>
>>>castor, freemarker and webmacro services will be deprecated (they will
>>>
>>not be
>>
>>>included in 3.0)
>>>
>>>if you have any wishes for the 2.2 release, speak now!
>>>
>>So will the 2.2 release contain the latest Intake developments?
>>
>
> yes.
>
So 2.2 will contain new features ?
Would it then be possible to add the following method to
TurbineVelocityService ?
/**
* Process the request and fill in the template with the values
* you set in the Context.
*
* @param context A Context.
* @param filename A String with the filename of the template.
* @param writer A Writer where we will write the process template as
* a String.
*
* @throws TurbineException Any exception trown while processing will be
* wrapped into a TurbineException and rethrown.
*/
public void handleRequest(Context context,
String filename,
Writer writer)
throws TurbineException
{
/*
* This is for development.
*/
if (pullModelActive && refreshToolsPerRequest)
{
TurbinePull.refreshGlobalTools();
}
try
{
Velocity.mergeTemplate(filename, context, writer);
}
catch(Exception e)
{
renderingError(filename, e);
}
finally
{
try
{
if (writer != null)
{
writer.flush();
}
}
catch (Exception e)
{
/*
* do nothing.
*/
}
}
}
This makes it actually possible to write a DirectOutputLayout in Velocity
that doesn't screw the servlet RequestDispatcher...
--
Raphael Luta - [EMAIL PROTECTED]
Vivendi Universal Networks - Paris
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
