On Oct 26, 2006, at 2:26 AM, Rick McGuire wrote:
I'd like to propose a couple of changes for the next release after
1.2 which should make JavaMail (and some other lame specs) easier
to use.
1) Add the ability to declare additional dependencies to the
configuration via the config.xml file. We probably want a way to
exclude a dependency and maybe add to the front of the dependency
list (unless remove re-add works). This is required to add a new
provider to the existing javamail configuration. Without this,
you must update every application to point to a new configuration
that contains your provider jar.
2) Add a "className" attribute to
org.apache.geronimo.mail.ProtocolGBean and all subclasses. If
this is set then, in addOverrides, we add a mail.${protocol}.class=
${className} to the properties object. There is no reason to add
this until item 1 is complete, since you can't extend the class
path, and would be very confusing to users.
The combination of the 2 sounds reasonable. 2) could be useful
without 1), if you're hand constructing your own mail
configuration, so it might be worth adding now.
In the mean time a user can just add this to select the default
protocol:
<gbean name="mail/MailSession"
class="org.apache.geronimo.mail.MailGBean">
<attribute name="properties">
mail.smtp.class=org.apache.geronimo.mail.NullTransport
</attribute>
</gbean>
-dain