Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 65970 invoked from network); 2 Jan 2007 16:57:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 2 Jan 2007 16:57:58 -0000 Received: (qmail 43942 invoked by uid 500); 2 Jan 2007 16:58:02 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 43875 invoked by uid 500); 2 Jan 2007 16:58:01 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@cocoon.apache.org List-Id: Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 43864 invoked by uid 99); 2 Jan 2007 16:58:01 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from [212.11.67.184] (HELO webmail.session.it) (212.11.67.184) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jan 2007 08:57:59 -0800 Received: from localhost (localhost.localdomain [127.0.0.1]) by webmail.session.it (Postfix) with ESMTP id 4A7912E64F4 for ; Tue, 2 Jan 2007 18:06:46 +0000 (UTC) X-DSPAM-Result: Innocent X-DSPAM-Processed: Tue Jan 2 18:06:45 2007 X-DSPAM-Confidence: 0.9997 X-DSPAM-Probability: 0.0000 X-DSPAM-Signature: 459a9f35189101804284693 X-DSPAM-Factors: 27, X-Virus-Scanned: amavisd-new at X-Spam-Score: -1.54 X-Spam-Level: Received: from webmail.session.it ([127.0.0.1]) by localhost (webmail.session.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sAKv9TGtrzhI for ; Tue, 2 Jan 2007 18:06:45 +0000 (UTC) Received: from [10.29.38.9] (unknown [10.29.38.9]) by webmail.session.it (Postfix) with ESMTP id AFDAB2B4F12 for ; Tue, 2 Jan 2007 18:06:45 +0000 (UTC) Message-ID: <459A8EDA.9010008@apache.org> Date: Tue, 02 Jan 2007 17:56:58 +0100 From: Simone Gianni User-Agent: Thunderbird 1.5.0.8 (X11/20061201) MIME-Version: 1.0 To: dev@cocoon.apache.org Subject: Re: Problems with writing sitemap components as spring beans References: <459376E7.5020002@apache.org> <45937D8D.6010506@apache.org> <45938218.4020100@apache.org> <45938443.3050501@apache.org> <459390E0.1010706@apache.org> In-Reply-To: <459390E0.1010706@apache.org> Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Old-Spam-Status: No, score=-1.54 tagged_above=-10 required=6.6 tests=[ALL_TRUSTED=-1.44, DSPAM_HAM=-0.1] Carsten Ziegeler wrote: > Reinhard Poetz wrote: > >> we could provide an abstract parent bean definition >> (http://static.springframework.org/spring/docs/2.0.x/reference/beans.html#beans-child-bean-definitions). >> >> > Yes, but this would also mean that all implementations inherit from an > abstract class we provide. This is not a big deal, I guess we can live > with that. > IIRC this is not *required* (thought is convenient in many cases). In an abstract bean definition you can declare only a property, only the class, only a factory method or any mix of the preceding and something more. Obviously if you say that there is a property named "thatStuff", it will search for setThatStuff, but that could be in a common interface and does not require that every subclass extends the same abstract base class. Simone