> > Don't use JDBCListserv unless you've some special reason > > having studied the code.
> From looking at the JDBCListserv code, it looks like it served as the > base class for something that wasn't released The ancient history is here: http://cvs.apache.org/viewcvs.cgi/james-server/src/org/apache/james/transpor t/mailets/Attic/ Looks like it was a direction never quite completed. FWIW, the member table has the right structure, but the wrong column names to work with AvalonListservManager. JDBCListserv could be managed by AvalonListservManager if the SELECT were changed, since AvalonListservManager supports storing subscriber lists with JDBC. Might be worth adding dynamic list support into the new List server from Mark, so that list definitions can come from a database or from data populated at config time. > The downside to the current listserv Mailets is that [whenever] > I need to start a new list, I have to make another entry in > config.xml, build a new james.sar, and restart James. No, you just need to make another entry in SAR-INF/config.xml and restart James. Yes, it would be nice if we could avoid restarting James, but that's about it. --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
