Aaron Knauf wrote:
[details:
http://nagoya.apache.org/eyebrowse/ReadMsg?[EMAIL PROTECTED]
.org&msgNo=6094]
> A structured mailet config would allow multiple header/property mappings
> to be configured for a single mailet instance, too.
Kenny Smith concured:
> I've only tried to work on 2 mailets so far, but the restriction
> of a name-value pair combo has come up in both of them. I would
> love to have arbitrary XML parsed into a dom, or have the values
> pulled into a bean, etc.
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).
> [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
Aaron, here is a hook for you to raise your proposal again for discussion.
> On the same note, is there a reason not to use a DTD/XSD for JAMES
> config?
How would you validate the configuration? How do you know which elements
are valid or necessary for a given attribute VALUE? :-)
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
