[prev in list] [next in list] [prev in thread] [next in thread] 

List:       logback-dev
Subject:    [logback-dev] [JIRA] Resolved: (LBCLASSIC-52) Allow multiple
From:       "Ceki Gulcu (JIRA)" <noreply-jira () qos ! ch>
Date:       2008-08-28 14:52:45
Message-ID: 1365488496.1219935165962.JavaMail.ceki () pixie
[Download RAW message or body]


     [ http://jira.qos.ch/browse/LBCLASSIC-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel \
]

Ceki Gulcu resolved LBCLASSIC-52.
---------------------------------

    Resolution: Won't Fix

SMTPAppender already supports multiple email destinations. You can invoke addTo() as \
many times as you want. The documentation of SMTPAppender already reads "Multiple \
recipients can be specified by using several <To> elements." 

I am marking this bug as WONT FIX as there is nothing to fix.

> Allow multiple addresses for "to" property of SMTPAppender
> ----------------------------------------------------------
> 
> Key: LBCLASSIC-52
> URL: http://jira.qos.ch/browse/LBCLASSIC-52
> Project: logback-classic
> Issue Type: Improvement
> Reporter: Andrey Utkin
> Assignee: Ceki Gulcu
> 
> SMTPAppender don`t allow to specify multiple addresses in single "to" property. So \
> that, it is (almost?) impossible to specify multiple "to" addresses via variable \
> substitution. We should know exact number of addresses (variables) to specify \
> appropriate quantity of <to> elements. But number of "to" addresses could be \
> changed during application using and differ from customer to customer. So, IMFO it \
> will be helpful to allow specifying multiple addresses in one <to> element. \
> Multiple addresses could be separated by comma, for example (as comma is not valid \
> character for email address). Right now we are using simple workaround. We subclass \
> SMTPAppender and overwrite addTo(): {code}
> @Override
> public void addTo(String to) {
> StringTokenizer st = new StringTokenizer(to, ",");
> while(st.hasMoreTokens()) {
> super.addTo(st.nextToken().trim());
> }
> }
> {code}
> This solution works just fine for us. May be it will be good to include this \
> feature in core logback too.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: \
                http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        
_______________________________________________
logback-dev mailing list
logback-dev@qos.ch
http://qos.ch/mailman/listinfo/logback-dev


[prev in list] [next in list] [prev in thread] [next in thread]