geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron Mulder" <ammul...@alumni.princeton.edu>
Subject Re: Start JavaMail by default in 1.1.1?
Date Wed, 09 Aug 2006 16:44:10 GMT
On 8/9/06, Matt Hogstrom <matt@hogstrom.org> wrote:
> Starting it is fine but it does require some customization as Aaron pointed out.  Will
the start be
> graceful enough that users will know that they need to customize it?  Perhaps a WARNING
message
> issues at startup if it hasn't been configured would be nice.

It doesn't always need to be configured even if you're using it as a
J2EE resource -- many Linux boxes come with an MTA already running, so
the default mail server of localhost may be perfectly reasonable.

Thanks,
     Aaron

> Rick McGuire wrote:
> > Aaron Mulder wrote:
> >> I don't see a great reason that we're not starting the JavaMail module
> >> by default.  Granted, the user may need to change the SMTP server, but
> >> it's going to be easier if they don't need to enable the module too
> >> (e.g. the console usually doesn't see disabled GBeans, and the
> >> load=false is easy enough to miss in config.xml).
> > I think this is probably a good idea.  Most of the problems I've seen
> > with users attempting to use javamail have been caused by the fact the
> > javamail module has not been started.  This usually manifests as a
> > provider resolution failure because the transport jars are not showing
> > up in the classpath.  Because the spec jars ARE there by default, this
> > error doesn't show up until it is used.
> >
> >
> >>
> >> What do you think?
> >>
> >> Thanks,
> >>     Aaron
> >>
> >
> >
> >
> >
>

Mime
View raw message