Re: [V3] Mailet/Matcher configuration

[Kenny Smith]

> Guys, have you looked at the exchange in [V3] Personal Item List?
> There is a proposal that the revised configuration look something
> like:

> <mailet class="Whatever">
> <matcher class="Whatever">
> <condition>whatever<condition/>
> <param name="x" value="y"/>
> <matcher/>
> <param name="a" value="b">
> <mailet/>
>
> Personally, I am very comfortable with XML, but Danny has indicated
> that he is unfavorably disposed towards complicating the Mailet API
> with full DOM access or the configuration file with more complex XML
> (e.g., namespaces).

My absolute perferred method would be similiar to the ActionForm concept in Struts. That I would define a bean that would be dynamically populated with my data. So if I had something like (matcher stuff excluded for now):

<mailet class="Foo">
<config>
<name type="String">Kenny</name>
<something type="int">3</something>
</config>
</mailet>

Then I could get the Config bean for my mailet, cast it to a MyFooConfig object and call getName() and getSomething() on it and it would return typed data.

I realize that this is very complicated, but I offer it as my best solution from the perspective of a developer (and I use the term lightly *smile*).

>> [Aaron's proposed] scheme would allow mailets to get their config in
>> one of 3 ways -
>> 1) As named properties
>> 2) As a DOM tree
>> 3) As a custom Config object

I like all three options and I'm partial to 2 (although I don't care for the namespaces complexity) and 3.

Kenny Smith
JournalScape.com



--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>