Hi Martin,
I think you've got a pretty good case for keeping handleRequest
around. I already gave it a reprieve in 2.0 and pushed back the
threatened removal to 2.1, but now you've got me reconsidering that.
I think your use-cases are stronger rationale for keeping it than my
thin reasons for being rid of it.
At this point, i would say keep using handleRequest. I think i'll
de-deprecate it. :)
thanks for the feedback. this kind of clear example is very helpful!
-nathan
On Tue, Nov 4, 2008 at 10:14 PM, Martin Thelian <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I'm trying to migrate my application to use then new functions fillContext +
> getTemplate instead using the deprecated function handleRequest.
>
> One of the problem is that I have usecases where I fetch a tool from the
> context, call some functions and if everything worked fine, the browser is
> redirected to a new location. But if an error occurs an error message is put
> into the context and displayed by the servlet using a given template.
>
> What is the best practice to do this with the new splitted fillContext and
> getTemplate functions? Do I really need to overwrite doRequest and generate
> the Context on my own?
>
> Furthermore I have usecases where I need to change the layout to use via
> context.put("layout", "plain.vm"); Of course I can do this in fillContext,
> but is this really context related? Because now I have the strange situation
> that I have to choose the template to use in getTemplate but the layout to
> use in fillContext.
>
> Regards,
> Martin
>
>
> ---------------------------------------------------------------------
> 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]
