Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Message-ID: <46A6E5BC.2070909@apache.org>
Date: Wed, 25 Jul 2007 07:55:08 +0200
From: Carsten Ziegeler <cziegeler@apache.org>
User-Agent: Thunderbird 2.0.0.5 (Macintosh/20070716)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: How to register MockProcessInfoProvider?
References: <46A5CBBC.8040604@tuffmail.com> <46A61B06.6010002@apache.org>
 <46A61EF4.3060300@apache.org> <46A67899.9020008@apache.org>
In-Reply-To: <46A67899.9020008@apache.org>
Content-Type: text/plain; charset=ISO-8859-2
Content-Transfer-Encoding: 7bit

Grzegorz Kossakowski wrote:

> 
> What about getParameters() sort of methods that enable you to have
> expressions like cocoon.request.parameters.param1 ?
> 
> Since ProcessInfoProvider returns implementation of HttpServletRequest
> there is no access to these methods. Any idea on this?
> 
Yes, this is an open question - we should avoid these methods if
possible :) Now, I can guess that you don't like the answer, but to have
general components which might be reusable outside of Cocoon we should
stick to available interfaces where possible.

Now, the request has a getParametersMap(), perhaps we could "somehow"
use this for cocoon.request.parameters? It would be great if we could
just use the servlet interfaces whereever possible. This makes a
transition later on much easier.

Carsten

-- 
Carsten Ziegeler
cziegeler@apache.org