Something bad in email sending ?

[Guillaume Bort]

Check these points:

1. Call send() without setting the ContentType: NullPointerException.
Wrong. It should say that the template is not found
2. Call send() putting text/plain as ContentType. It tries to find the
methodName.txt template OK
3. Call send() putting text/plain;charset=utf-8 as ContentType. It
tries to find the methodName.html template. Wrong. Maybe nobody
thought about using "charset=" in the contentType.
4. Call send() putting text/html as ContentType. It tries to find the
methodName.html template OK
5. Call send() with any other contentType it tries to find an html
template. Well, I have no problem with this.

[Nicolas Leroux (nicolas-lunatech)]

In the 1.1 version I am planning to use the jakarta commons email library to have something a bit more consistent. Essential it will become send(email) instead of the long and error prone send(a,b, c, d, e, f, ... x, z y) methods. Anyone against it or has a better suggestion? (I will send the same proposal on the google group).

[Guillaume Bort (guillaume-bort)]

Well no it's ok to use jakarta commons email if it solve these problems.

On Wed, Dec 16, 2009 at 9:31 AM, Nicolas <email address hidden> wrote:
> In the 1.1 version I am planning to use the jakarta commons email
> library to have something a bit more consistent. Essential it will
> become send(email) instead of the long and error prone send(a,b, c, d,
> e, f, ... x, z y) methods. Anyone against it or has a better suggestion?
> (I will send the same proposal on the google group).
>
> ** Changed in: play
>     Assignee: (unassigned) => Nicolas (nicolas-lunatech)
>
> --
> Something bad in email sending ?
> https://bugs.launchpad.net/bugs/497152
> You received this bug notification because you are a member of play
> framework developers, which is subscribed to play framework.
>