cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Simone Gianni (JIRA)" <>
Subject [jira] Updated: (COCOON-1818) SendMailTransformer misses closing tag when recipient address is malformed
Date Thu, 30 Mar 2006 14:34:26 GMT
     [ ]

Simone Gianni updated COCOON-1818:

    Attachment: sendmail-exceptions2.diff

This patch applies the solution number 3 : for every call to the sendMail() method a result
element is always generated. It will contain an error, an exception, or the common email sent

This changes the produced XML in many ways :
- The error element was not conained in a result before this patch.
- The exception element was or was not contained in a result before this patch (and this caused
the main problems)

So consider that after applying you'll probably have to change the XSL that transforms the

If a mail is not sent, it should not stop sending all the others, unless a SAXException is
received (in that case the pipeline is probably broken, so there's nothing cocoon can do about
it). Maybe you've seen it stopping because of the inconsistent XML, which caused a SAXException,
which stops everything.

P.S. this patch is not a delta from the previous one, so you should revert the file on which
you applied the previous patch and the apply this one on the clean reverted file.

> SendMailTransformer misses closing tag when recipient address is malformed
> --------------------------------------------------------------------------
>          Key: COCOON-1818
>          URL:
>      Project: Cocoon
>         Type: Bug
>   Components: Blocks: Mail
>     Reporter: Jasha Joachimsthal
>  Attachments: sendmail-exceptions.diff, sendmail-exceptions2.diff
> When a recipient address contains an illegal character (, ; <space> a@b@com etc),
an exception is being thrown by method sendMail(List newAddresses, Transport trans).
> The execution of the try in method sendMail() is stopped which may have created a <email:result>
> No </email:result> end tag is created when this occurs.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message