I don't think that we're recommending use of Sun JavaMail now, are we?
I think that's just a way that we can run some type of provider to
validate the javamail admin portlet until we can get things straightened
out with our own smtp provider. After all, the patch for the admin
portlet hasn't even been integrated yet.
There is work happening to get the geronimo smtp provider revived and
functional again with the hope that we will be able to include it and
the admin portlet in M5.
I guess if we can't resolve the problems with the provider in time for
M5 then we need to decide if we want to include the Admin function with
manual directions for how to include the Sun JavaMail smtp or other
provider ... or if we just want to wait on the admin javamail portlet
itself until we have a self contained solution.
Aaron Mulder (JIRA) wrote:
Bundle a JavaMail implementation & SMTP provider
------------------------------------------------
Key: GERONIMO-944
URL: http://issues.apache.org/jira/browse/GERONIMO-944
Project: Geronimo
Type: Improvement
Components: mail
Versions: 1.0-M4
Reporter: Aaron Mulder
Fix For: 1.0-M5
I'm not sure what the state is of our JavaMail implementation. I know we have
our own spec JAR and I think I've heard that we have our own SMTP provider, but
that it's not part of the Geronimo distribution and as a result the Sun
JavaMail provider is recommended. I'd like to straighten this out for M5 so we
can provide basic JavaMail resource mapping (at least for outgoing mail via
SMTP) as part of the standard package.
If this is not possible for some reason, please retarget this issue to 1.0 and
suggest a path forward. Thanks.
--
Joe Bohn
[EMAIL PROTECTED]
"He is no fool who gives what he cannot keep, to gain what he cannot lose."
-- Jim Elliot
