Return-Path: 
 <dev-return-99207-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@www.apache.org
Received: (qmail 57482 invoked from network); 15 Apr 2008 08:52:23 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 Apr 2008 08:52:23 -0000
Received: (qmail 33557 invoked by uid 500); 15 Apr 2008 08:52:23 -0000
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 33499 invoked by uid 500); 15 Apr 2008 08:52:23 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
List-Post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
List-Id: <dev.cocoon.apache.org>
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 33487 invoked by uid 99); 15 Apr 2008 08:52:23 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2008 01:52:23 -0700
X-ASF-Spam-Status: No, hits=1.2 required=10.0
	tests=SPF_NEUTRAL
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Received: from [88.198.46.98] (HELO indoqa.com) (88.198.46.98)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 15 Apr 2008 08:51:29 +0000
Received: from [192.168.1.32] (chello062178239020.5.15.vie.surfer.at
 [62.178.239.20])
	by indoqa.com (Postfix) with ESMTP id 894D02547AB
	for <dev@cocoon.apache.org>; Tue, 15 Apr 2008 10:51:50 +0200 (CEST)
Message-ID: <48046CA5.7040902@apache.org>
Date: Tue, 15 Apr 2008 10:51:49 +0200
From: Reinhard Poetz <reinhard@apache.org>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: dev@cocoon.apache.org
Subject: Re: Use case for ${org.apache.cocoon.blocks.[BLOCK_NAME].resources}
 style properties
References: <47FDFBA7.7090608@apache.org> <47FDFF4C.6090407@apache.org>
In-Reply-To: <47FDFF4C.6090407@apache.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-Virus-Checked: Checked by ClamAV on apache.org

Carsten Ziegeler wrote:
> Reinhard Poetz wrote:
>>
>> I've just started to move the deployment of blocks into a 
>> ServletContextListener and came across a (for me) unkown feature that 
>> gives access to the path of blocks in Spring properties:
>>
>> This feature was introduced by Carsten as part of this SVN commit 
>> http://cocoon.markmail.org/message/slrelbwbej3xyryq
>>
>> And here the text from changes.xml:
>>
>> <quote>
>>   Improved the DefaultBlockResourcesHolder to act like a
>>   PropertyPlaceholderConfigurer. This allows access to the path of the 
>> deployed
>>   blocks in the configuration files through properties like
>>   ${org.apache.cocoon.blocks.[BLOCK_NAME].resources}.
>> </quote>
>>
>> What's the use case for this feature? (If there is none [anymore], I 
>> don't have to migrate it ... ;-)  ).
>>
> I only add features if there's a use case :)
> This is needed for the hsqldb block to specify where the db files are 
> located.
> But still, it should be possible to decouple this - if the servlet 
> context listener deploys the stuff and makes the map of deployed blocks 
> available, a property configurer can pick it up and still replace the 
> properties.

I don't want to make the Spring configurator depend on the block deployer in the 
future.

Is it possible to register more than one property configurer?

-- 
Reinhard P�tz                            Managing Director, {Indoqa} GmbH
                           http://www.indoqa.com/en/people/reinhard.poetz/

Member of the Apache Software Foundation
Apache Cocoon Committer, PMC member, PMC Chair        reinhard@apache.org
_________________________________________________________________________