Re: [seam-dev] Seam 3 Mail Feedback Follow-up

Now that I think about it, implementing it as an interface would cut the method count down on the MailMessage/VelocityMailMessage interfaces quite a bit...and from a maintenance perspective I'm worried about those getting too large since many of the methods have to be replicated on MailMessage + VelocityMailMessage and any future Templating systems we support. Or we just drop the builder pattern all together. I skeptical of someone implementing the EmailAttachment interface on their own, but it can't hurt and will make the api cleaner.