I am aware that that is what matchers do. However the filters that I am defining (and I simplified for the sake of the example I provided in the original email) are data driven in number and type and their configuration is stored in a database. They can be updated while the mail server is running...
So I can't write matchers and create the config.xml workflow that determines which matcher gets called first, followed by which other matcher in advance. Also, basing a solution on matchers and mailets in this way restricts me to using james. If I decide at some point I would like to use some other mail server I cannot easily translate. In any case, this still doesn't get around the fact, unless I am misunderstanding something fundamental, that MimeMessageWrapper contains a number of issues. ANY mailet that calls one of the MimeMessageWrapper set functions that have this problem is going to not work if it then uses the corresponding get. The way in which I am using Matchers and Mailets is largely irrelevant to the point I was trying to make, which is about the inconsistancies in the observed state of the MimeMessage Neill -----Original Message----- From: Danny Angus [mailto:[EMAIL PROTECTED] Sent: 26 November 2003 09:04 To: James Users List Subject: Re: LOTS of MimeMessageWrapper issues... bugs? Importance: Low > I have written a mailet in which I am trying to filter a subset of the > recipents of a MimeMessage so that they can be processed differently > from the rest. This is what Matchers do. If the existing matchers don't provide the filtering you need you should write new matchers rather than try to replicate this function inside a mailet. A mail which matches one criteria can be processed or sent to another processor pipleine where it can be tested again and processed or sent to yet another processor pipeline ad-nauseam. d. ************************************************************************ *** The information in this e-mail is confidential and for use by the addressee(s) only. If you are not the intended recipient (or responsible for delivery of the message to the intended recipient) please notify us immediately on 0141 306 2050 and delete the message from your computer. You may not copy or forward it or use or disclose its contents to any other person. As Internet communications are capable of data corruption Student Loans Company Limited does not accept any responsibility for changes made to this message after it was sent. For this reason it may be inappropriate to rely on advice or opinions contained in an e-mail without obtaining written confirmation of it. Neither Student Loans Company Limited or the sender accepts any liability or responsibility for viruses as it is your responsibility to scan attachments (if any). Opinions and views expressed in this e-mail are those of the sender and may not reflect the opinions and views of The Student Loans Company Limited. This footnote also confirms that this email message has been swept for the presence of computer viruses. ************************************************************************ ** --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
