commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Commons Wiki] Update of "Email" by BenSpeakmon
Date Mon, 20 Aug 2007 23:18:19 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Commons Wiki" for change notification.

The following page has been changed by BenSpeakmon:
http://wiki.apache.org/jakarta-commons/Email

The comment on the change is:
- update feature status and release plan goals

------------------------------------------------------------------------------
  
  ''(BenSpeakmon) One of the MimeMessage constructors in JavaMail (both 1.3 and 1.4) already
does this, BTW. I'm not sure this is something that falls within commons-email's scope. The
commons-email API, I think, is for the common cases where you just want to build and send
an email without needing the power (or complexity) of JavaMail. If you're already pulling
messages from an email server, I don't know why you wouldn't just use JavaMail for manipulating
it -- the power and complexity is just what you need for those kinds of jobs. And it doesn't
seem worth the trouble to duplicate any of that code in commons-email when the existing code
works just fine. I'd recommend WONTFIXing this one.''
  
+ [https://issues.apache.org/jira/browse/EMAIL-6 EMAIL-6]: Allow attaching one subclass of
Email to another.
+ 
+ ''(BenSpeakmon) I'm not convinced that it's useful to support attaching one subclass of
Email to another subclass -- that is, the original report creates an HtmlEmail and then wants
to attach that to a MultiPartEmail. The current design of commons-email would make this very
tricky, but aside from that I don't see the general usefulness of doing so. One case where
I do see a use for this would be when the user wants to attach a MimeMessage he got from somewhere
(like a server or a filestore) to a subclass of Email. This would mean adding MultiPartEmail.addMimeMessage()
methods which would then be attached like the current addPart() methods. (We'd have to have
different names, since MimeMessage doesn't share a common interface ancestor with MimeMultipart.)
There's still a problem, though; such a MimeMessage would have arbitrarily complex content
in it. It could be multipart, HTML text, full of attachments, etc., and there's no way to
know what really needs to be attached.
+ 
+ I think that this has to fall into that class of problems that would be better served with
JavaMail, so I'd recommend this be wontfixed.''
+ 
  = Open issues (last updated Jun 12 2007) =
  
  These are the currently open issues organized according to category.
  
  == New feature requests ==
- 
- [https://issues.apache.org/jira/browse/EMAIL-6 EMAIL-6]: Allow attaching one subclass of
Email to another.
- 
- ''(BenSpeakmon) I'm not convinced that it's useful to support attaching one subclass of
Email to another subclass -- that is, the original report creates an HtmlEmail and then wants
to attach that to a MultiPartEmail. The current design of commons-email would make this very
tricky, but aside from that I don't see the general usefulness of doing so. One case where
I do see a use for this would be when the user wants to attach a MimeMessage he got from somewhere
(like a server or a filestore) to a subclass of Email. This would mean adding MultiPartEmail.addMimeMessage()
methods which would then be attached like the current addPart() methods. (We'd have to have
different names, since MimeMessage doesn't share a common interface ancestor with MimeMultipart.)
There's still a problem, though; such a MimeMessage would have arbitrarily complex content
in it. It could be multipart, HTML text, full of attachments, etc., and there's no way to
know what really needs to be attached.
- 
- I think that this has to fall into that class of problems that would be better served with
JavaMail, so I'd recommend this be wontfixed.''
  
  [https://issues.apache.org/jira/browse/EMAIL-65 EMAIL-65]: Improve HtmlEmail MIME layout.
  
@@ -74, +74 @@

   * Get maven 2 build to the point where it can do everything the m1 build does
   * Remove the m1 build
   * Do a javadoc pass; leave no public/protected member undocumented
-  * Deprecate unused public/protected members
   * Run complete build, test, and package cycle on JDK 1.4, 5, and 6
   * Upload my gpg key for signing the release
  

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
For additional commands, e-mail: dev-help@commons.apache.org


Mime
View raw message