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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]