Aaron,
You wrote:
> This subject has come up a few times. I suggested an approach to
> handling mailet and matcher config better, as did a few others. I even
> offered to write it. However, due to the distinct lack of enthusiasm
> for my (or any other) solution, I lost interest. I could be convinced
> to revisit this if some of the committers indicated that they were
> interested.
Without checking I think that the perceived lack of interest was due to a deferal of
these issues to v3.
Now that v3 is proceding go ahead with it, I'm indicating that I'm interested and will
support your contribution.
Check the wiki for others' opinions on this (and other) v3 topics, and post your
ideas, or code, here for discussion & inclusion.
AFAICR we reached some concensus on the following style.. which would allow us to
produce a processor DTD (example attached) and standardise every mailet config.
I can't remember what other suggestions/arguments were raised, but you could check the
mail archive.
<mailet .............>
<matcher class="...">
<condition>...</condition>
<parameters>
<parameter name="..."></parameter>
<parameter name="..."></parameter>
</parameters>
</matcher>
<matcher class="...">
<condition>...</condition>
<parameters>
<parameter name="..."></parameter>
<parameter name="..."></parameter>
</parameters>
</matcher>
<parameters>
<parameter name="..."></parameter>
<parameter name="..."></parameter>
</parameters>
</mailet>
d.
<!ELEMENT processor (mailet)+>
<!ATTLIST processor
class CDATA #REQUIRED
name CDATA #REQUIRED
>
<!ELEMENT mailet (matcher,parameters)*>
<!ATTLIST mailet
class CDATA #REQUIRED
>
<!ELEMENT matcher (condition,parameters)*>
<!ATTLIST matcher
class CDATA #REQUIRED
>
<!ELEMENT condition (#PCDATA)>
<!ELEMENT parameters (parameter)+>
<!ELEMENT parameter (#PCDATA)>
<!ATTLIST parameter
name CDATA #REQUIRED
>
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
