Ok, I'll try to use your approach in my code to see how it works. Actually you must be right because what I am doing now doesn't use matchers at all, that logically resulted for me in my proposal (since I've been using that extensively in my architecture where there are no matchers and therefore there is no risk to flatten namespaces). Andrei
----- Original Message ----- From: "Noel J. Bergman" <[EMAIL PROTECTED]> To: "James Developers List" <[EMAIL PROTECTED]> Sent: Saturday, May 18, 2002 11:36 PM Subject: RE: James -> Phonix 4.0aX (minor changes) > Andrei, > > Another alternative to your: > > <mailet ...> > <addSubject enable="true" truncate="10"/> > </mailet> > > could be: > > <mailet ...> > <mailet-config:addSubject enable="true" truncate="10"/> > </mailet> > > Similarly, my: > > <mailet matcher="Foo[=cond]" class="Bar"> > <matcher-config> > <tagname>value</tagname> > </matcher-config> > <mailet-config> > <tagname>value</tagname> > </mailet-config> > </mailet> > > could be: > > <mailet matcher="Foo[=cond]" class="Bar"> > <matcher-config:tagname>value</matcher-config:tagname> > <mailet-config:tagname>value</mailet-config:tagname> > </mailet> > > Unqualified tags would be assumed, for compatibility with previous releases > of James, to be part of the mailet configuration. > > --- Noel > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
