Return-Path: 
 <commons-dev-return-49304-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 6086 invoked from network); 4 Apr 2004 12:13:15 -0000
Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12)
  by minotaur-2.apache.org with SMTP; 4 Apr 2004 12:13:15 -0000
Received: (qmail 70718 invoked by uid 500); 4 Apr 2004 12:13:10 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 70650 invoked by uid 500); 4 Apr 2004 12:13:09 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:commons-dev-subscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 70635 invoked from network); 4 Apr 2004 12:13:09 -0000
Received: from unknown (HELO smtp-out4.blueyonder.co.uk) (195.188.213.7)
  by daedalus.apache.org with SMTP; 4 Apr 2004 12:13:09 -0000
Received: from [10.0.0.2] ([82.38.65.173]) by smtp-out4.blueyonder.co.uk with
 Microsoft SMTPSVC(5.0.2195.5600);
	 Sun, 4 Apr 2004 13:13:10 +0100
Mime-Version: 1.0 (Apple Message framework v613)
Content-Transfer-Encoding: 7bit
Message-Id: <6E9CDE0F-8631-11D8-896F-003065DC754C@blueyonder.co.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
From: robert burrell donkin <robertburrelldonkin@blueyonder.co.uk>
Subject: [betwixt] extensible optional parameters in .betwixt file 
Date: Sun, 4 Apr 2004 13:13:07 +0100
X-Mailer: Apple Mail (2.613)
X-OriginalArrivalTime: 04 Apr 2004 12:13:10.0851 (UTC)
 FILETIME=[325DA930:01C41A3E]
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N

when discussing adding entries to the .betwixt file to allow users to 
choose whether a property should output CDATA or escaped character 
data, i indicated that i'd prefer not to start adding extra elements to 
the .betwixt file that only applied to certain strategies and 
configuration and instead look to add an extensible system for optional 
parameters.

my proposed name for the tag is 'option' (since property could be 
confused with the property on the bean). the name and value (for the 
parameter) will be the content of enclosed tags with those names (i 
prefer attributes but suspect that sooner or later large values will be 
needed). betwixt will read these and add the name-value pairs to the  
appropriate descriptor. strategies (and so on) should be able to read 
these values and interpret them freely.

for example:

<info ...>
...
	<element ...>
		<option>
<name>org.apache.commons.betwixt.content-encoding</name>
<value>CDATA</value>	
		</option>
	</element>
...
</info>

these options would be seen as hints rather than declarations. i mean 
by this that different configurations of betwixt would be free to 
behave differently - or ignore them completely. unlike the other 
(declarative) elements who presence indicates a contract.

comments welcomed.

i have some additional ideas on inheritance which i'll outline later 
(if you've been wondering about that).

- robert


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org