Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cocoon-dev@xml.apache.org
Date: Mon, 22 Oct 2001 15:45:17 +0200
From: Christian Haul <haul@dvs1.informatik.tu-darmstadt.de>
To: cocoon-dev@xml.apache.org
Subject: Re: [RT] New validator and propagator infrastructure
Message-ID: <20011022154517.F2194@bremen.dvs1.informatik.tu-darmstadt.de>
Reply-To: haul@informatik.tu-darmstadt.de
References: <20011022152026.A16582@renie.dyndns.org>
 <005d01c15afe$f891c3e0$0101a8c0@paolo>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
In-Reply-To: <005d01c15afe$f891c3e0$0101a8c0@paolo>;
 from lavoro@arsenio.net on Mon, Oct 22, 2001 at 03:39:27PM +0200
Organization: Databases and Distributed Systems Group,
 Darmstadt University of Technology

On 22.Oct.2001 -- 03:39 PM, Paolo wrote:
> You are right: a checkbox value, as seen with Vadim, is a string with a
> value of 'on', when selected. But a session or a request boolean
> attribute is an object, not a string. So we should process the source
> parameter differently depending by its source (request parameter or
> cookie are strings), and application/request/session attributes are
> objects.

So, what if the part responsible for retrieving the object converts it
to an object? We would only have to deal with objects for the
validation then.

	Chris.

-- 
C h r i s t i a n       H a u l
haul@informatik.tu-darmstadt.de
    fingerprint: 99B0 1D9D 7919 644A 4837  7D73 FEF9 6856 335A 9E08

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org