From dirkx@mobile.webweaving.org Sun Apr 16 23:49:02 2000 Return-Path: Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 46777 invoked from network); 16 Apr 2000 23:49:02 -0000 Received: from dhcp.207.44.198.86.salon.com (HELO mobile.webweaving.org) (207.44.198.86) by locus.apache.org with SMTP; 16 Apr 2000 23:49:02 -0000 Received: (from dirkx@localhost) by mobile.webweaving.org (8.9.3/8.9.3) id BAA03488; Mon, 17 Apr 2000 01:47:06 +0200 (CEST) (envelope-from dirkx) Date: Mon, 17 Apr 2000 01:47:06 +0200 (CEST) From: Dirk-Willem van Gulik X-Sender: dirkx@vaio.ispra.webweaving.org To: cocoon-dev@xml.apache.org Subject: Re: Image Serializers In-Reply-To: <38FA46DA.65D9F31A@apache.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N On Mon, 17 Apr 2000, Stefano Mazzocchi wrote: > You failed to see that if an object implements _both_ ImageEncoder and > Configurable is able to perform image encoding and have configurable > properties. No, but that is configuration; I was more concerned by behavour at run time. And am not convinced that a pure config interface is the solution to that as their might well be other interaction in the publication path; say for attaching a digital kiddie-safe seal or on the fly conversion to some PDA b&w safe pixmap. > The JavaBean pattern might be good for automatic introspection (IDEs, or > Ant-like XML mapping), but Cocoon never uses the JavaBean pattern (and > people never seemed to be missing it!) Thus ? Dw